PingAccess Agent for Apache (Windows) release notes
These release notes summarize the changes in current and previous PingAccess Agent for Apache (Windows) updates. Updated July 18, 2024.
PingAccess Agent for Apache (Windows) 1.6 (July 2024)
Cache multiple token-types for Web + API applications
New PA-15516
If you use a Web + API application, the vnd-pi-resource-cache PingAccess agent protocol (PAAP) header now contains an additional path so Web + API applications can cache both cookie and authorization header token-types. For more information, see the Cache multiple token-types for Web + API applications entry in the PingAccess 8.1 release notes, and the agent.cache.defaultTokenType property on the Windows agent configuration page.
|
Existing agent environments ignore the new To see the performance boost, upgrade to PingAccess 8.1 and upgrade to the latest version of the Windows agent. Otherwise, continue to use an earlier agent version. |
Block bad characters in Apache and IIS agent deployments
New PAA-251
Configure a PingAccess Apache agent or the PingAccess agent for IIS to block requests that contain bad characters in the URI, query parameters, form parameters, or request body without having to reach out to PingAccess for a decision.
Added eight new properties to each agent:
-
agent.request.block.xss.characters -
agent.request.block.uri.characters -
agent.request.block.query.characters -
agent.request.block.form.characters -
agent.request.block.xss.http.status -
agent.request.block.uri.http.status -
agent.request.block.query.http.status -
agent.request.block.form.http.status
Learn more in the configuration page for your agent:
|
For large scale or more complex blocking decisions, it’s best practice for the agent to reach out to PingAccess for a decision. |