If a Web Agent on an IIS 6.0 web server returns a 404 Not found error in response to a resource request, or if the Web Agent is not being called properly by the IIS 6.0 web server, open the IIS console and ensure that Wildcard Application mapping has been enabled and is configured to refer to the Web Agent DLL. Also, ensure that the Verify file exists check box is cleared before the mapping is enabled.
You can determine whether the custom responses from your Web Agent comply with P3P response headers with the following parameter:
Determines whether custom responses comply with the Platform for Privacy Preferences Project (P3P) response headers. P3P compact policies use tokens representing the specific elements from the P3P terminology. If you set the P3PCompactPolicy parameter to the appropriate policy syntax, it ensures that custom responses are set with the correct P3P response header when a P3P compact policy is specified for the Web Agent.
Default: No default
Example: NON DSP COR CURa TAI (these represent: none, disputes, correct, current/always, and tailoring, respectively)
To accommodate P3P compact policies, add an appropriate policy syntax to the P3PCompactPolicy parameter.
|
Copyright © 2012 CA.
All rights reserved.
|
|