Backward Compatibility Settings

This content describes settings that you can use to manage the backward compatibility of your agent.
sm1252sp1
This content describes settings that you can use to manage the backward compatibility of your agent
.
Accommodate Legacy URL Encoding
The legacy URL encoding used by CA uses dollar sign ($) characters. If the dollar signs cause problems, you can make the Web Agent use hyphen (-) characters instead of dollar signs with the following parameter:
LegacyEncoding
Forces the Web Agent to replace any dollar sign ($) characters in legacy URLs with a hyphen (-). Doing this also ensures backwards comparability with MSR, Password Services, and DMS. When this parameter is set to no, a Web Agent converts the string $SM$ to -SM-. When this parameter is set to yes, the Web Agent does
not
convert the dollar sign ($) character.
Default:
(Framework Agents) No
Default:
(Traditional Agents) Yes
To encode legacy URLs using hyphens instead of dollar signs, set the value of the LegacyEncoding parameter to no.
Choose How Content Types Are Transferred in POST Requests
If you are using an Apache web server, you can control how content is transferred to the server during POST requests with the following parameter:
LegacyStreamingBehavior
Specifies how content is transferred to the server during POST requests. When the value of this parameter is set to yes, all content types are streamed,
except
for the following content types:
  • text/xml
  • application/x-www-form-urlencoded
When the value of this parameter is set to no, all content types are spooled.
Default
: No
To stream most types of content in POST requests, change the value of the LegacyStreamingBehavior parameter to yes.
Accommodate Testing Tools That Do Not Send HOST Headers
The
CA Single Sign-On
Web Agent uses the value of the HOST header in an HTTP request to determine the following settings:
  • Agent name
  • Server name
  • Server IP address
By default, Web Agents only accept HTTP requests that use HOST headers. This restriction poses problems for some testing tools that do not send HOST headers, because the Web Agent rejects those requests. To accommodate testing tools that do not send HOST headers, set the following agent configuration parameter for your agent:
DefaultHostName
Defines a value for the HOST header. Add this parameter to your Agent Configuration Object or LocalConfig.conf file if you are using a testing tool that sends HTTP requests without HOST headers. If this parameter is not set, the Web Agent
only
accepts requests with HOST headers.
Default
: None (blank)
Example
: webserver.example.com
Once set, the Web Agent substitutes the DefaultHostName value for any HTTP request without a HOST header.