We are running SSO Access Gateway as a SSO front end to a web application called Pega.
In the server.log for AG, we get the following message on certain page requests:
[ERROR] - org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected
[01/Feb/2021:19:55:23-110] [ERROR] - at org.apache.http.impl.io.ChunkedInputStream.getChunkSize(ChunkedInputStream.java:266)
The associated log message in the httpd log file is:
w.x.y.79 - - [01/Feb/2021:19:55:23 +0000] "GET /prweb/PRPushServlet/[email protected]!?PZSRVRPSH=true&portalName=Developer&clientID=CXtwZH1BQUFBQVVFNE1ZQnlWeFRSaXBGWnZ3UVF2TFMwTld3SHJ5MEdmQzBKeThISUVhSUF1UDVBQkZVc1F6MlkyU3Y4WGJHUDlnPT0%3D&X-Atmosphere-Transport=close&X-Atmosphere-tracking-id=78aa819f-f3a8-4473-8501-644c17322439&_=1612209323131 HTTP/1.1" 200 -
This does not appear to impact the end users who access the Pega application behind SSO Acc Gateway, but we would like to see if we can eliminate the messages.
The back end server is not sending the expected zero length closing chunk resulting in this error.
Release : ALL
Component : ACCESS GATEWAY
Access Gateway will still process these requests, but ultimately the back end host should be corrected to send the expected chunk and thus be in compliance with HTTP standards.