Disable HTTP escaping and unescaping of URIs
|
WSupported on Windows
|
USupported on Unix
|
VSupported on OpenVMS
|
NSupported in Synergy .NET
|
Setting HTTP_NOESCAPE turns off automatic escaping and unescaping of URIs by the Synergy HTTP document transport API.
Value
Any value.
Discussion
In version 8.3, we added automatic escaping of certain unescaped characters in a URI by %HTTP_CLIENT_GET and %HTTP_CLIENT_POST and automatic unescaping of any escape codes in a URI by %HTTP_SERVER_RECEIVE. If you had already implemented your own escape mechanisms prior to this feature being added, you may want to set HTTP_NOESCAPE to avoid breaking your existing code.
|
If you set HTTP_NOESCAPE, you will need to translate characters such as spaces manually. For instance, in order to pass a URI that contains spaces, you must first convert each space to the characters “%20” in the URI. To get my big file.html from myserver, for example, you would pass the following URI to %HTTP_CLIENT_GET: "http://myserver/my%20big%20file.htm" |
Unsetting or clearing HTTP_NOESCAPE will turn automatic escaping back on again.
Setting location
The environment.
Used by
Synergy HTTP document transport API
See also
- %SYN_ESCAPE_HANDLE routine
- %SYN_UNESCAPE_HANDLE routine
- %HTTP_CLIENT_GET routine
- %HTTP_CLIENT_POST routine
- %HTTP_SERVER_RECEIVE routine
Examples
On Windows,
set HTTP_NOESCAPE=1
