MaxHeaderSize for Access Gateway.
Article ID: 8032
Updated On:
Products
Issue/Introduction
Groups are being pulled into the HTTP Header. A large number of groups is causing the HTTP Header to be very Large. The CA Gateway server is failing to process the requests.
Environment
CA Access Gateway: 12.8.x and 12.9 (Applicable to all the supported releases)
Cause
CA Gateway is bundled with Tomcat and Apache Web Server. The HTTP Connector is not used between Tomcat and Apache, instead the AJP Connector is used. "maxHttpHeaderSize" is a valid attribute in the HTTP Connector, but not the AJP Connector.
The AJP Protocol is "Packet Oriented". There is no 'maxHttpHeaderSize' in the AJP protocol. Instead the AJP protocol simply uses 'max_packet_size'. 'max_packet_size' doesn't limit an aspect of the packet, such as the HTTP Header. It limits the entire packet. When large HTTP headers are involved, the entire packet size exceeds the default limit.
Resolution
Worker.ajp13.max_packet_size needs to be increased.
Please follow the below steps to make the required changes.
1) Logon to the CA Gateway host
2) Browse to the 'Server.conf' File
-> Default Path:
Windows: <Install_Dir>\CA\secure-proxy\proxy-engine\conf\server.conf
UNIX: <Install_Dir>/CA/secure-proxy/proxy-engine/conf/server.conf
3) Locate the following section:
#'max_packet_size': This attribute sets the maximum AJP packet size in Bytes. The maximum value is 65536.
#This same value will be used as 'packetSize' attribute for the AJP connector on the Tomcat side.
worker.ajp13.max_packet_size=16384
4) Modify the 'max_packet_size' value to accommodate the total size of the packets with the additional Header Data.
NOTE: The maximum value is 65536
5) Restart the CA Gateway server (Tomcat).
Additional Information
Feedback
