Tech Tip : CA Single Sign-On : smagent.log error Input filter pre-fetch read error - 'Content data is not available'

Document created by Osarobo_Idehen Employee on Aug 18, 2017
Version 1Show Document
  • View in full screen mode

Question:


Why are observing multiple entries of below message in the webagent log?

[CSmHttpPlugin.cpp:2224][WARNING][sm-HTTPAgent-00190] Unable to process SMSESSION cookie.

 

[SmApache24WebFilterCtxt.cpp:551][ERROR][sm-AgentFramework-00060]Input filter pre-fetch read error - 'Content data is not available'



Environment:

 

12.52.x webagent / Apache2.x



Answer:


The above message is logged if you have legacy applications (that does not support HTTP 1.1) running on the Apache Web Server.

To use Legacy Applications with an Apache Web Agent, update the following ACO parameter:

LegacyTransferEncoding

This parameter specifies the type of message encoding used by the Web Agent. When the value of this parameter is set to no, transfer-encoding is supported.

When the value of this parameter is set to yes, content encoding is used. The transfer-encoding header is ignored and only the content-length header is supported.

Default: No

To use legacy applications with an Apache Web Server, set the value of the LegacyTransferEncoding parameter to yes.

 

Important! If you set the value of this parameter to yes, these features will not work: Federation; preservation of POST data longer than 4 KB; and large certificates may not be recognized

 


Additional Information:


https://docops.ca.com/ca-single-sign-on/12-52-sp1/en/configuring/web-agent-configuration/advanced-configuration-settings/apache-web-server-settings

 

 

KD : TEC1970189

Attachments

    Outcomes