I am running Apache v2.2.13 on RHEL 5.3 My network team has an F5 load balancer which is performing SSL termination. The hostname I am using is configured to reside on the load balancer (example: https://domain.company.com). The load balancer sends all data over clear-text internally to the Apache webserver. The Apache webser is utilizing mod_proxy and proxying over the entire root "/" to the application server. For me this works perfectly on Firefox v3.5.7. It does not work properly on Internet Explorer v6.0 for me. For my co-worker it does not work on Firefox v3.5.8 or his IE 6.0. We note that on the failed systems, the URL session ";jsessionid=cjutvzks9ljs" doesnt seem to pass through? If we remove that sessionid and re-submit the URL, it will create a new session and work that one time. Here is some data from the apache log [Tue Mar 16 10:37:21 2010] [error] [client 111.222.333.444] (70014)End of file found: proxy: error reading status line from remote serv er backend-app-server.company.com, referer: https://domain.company.com/MyProfile/MyDetails/MyDetails.do;jsessionid=d5un86mii64h [Tue Mar 16 10:37:21 2010] [error] [client 111.222.333.444] (70014)End of file found: proxy: error reading status line from remote serv er backend-app-server.comapny.com, referer: https://domain.company.com/MyProfile/MyDetails/MyDetails.do;jsessionid=d5un86mii64h [Tue Mar 16 10:37:21 2010] [error] [client 111.222.333.444] (70014)End of file found: proxy: error reading status line from remote serv er backend-app-server.company.com, referer: https://domain.company.com/MyProfile/MyDetails/MyDetails.do;jsessionid=d5un86mii64h [Tue Mar 16 10:37:21 2010] [error] [client 111.222.333.444] proxy: Error reading from remote server returned by /MyProfile/index/index. do;jsessionid=d5un86mii64h, referer: https://domain.company.com/MyProfile/MyDetails/MyDetails.do;jsessionid=d5un86mii64h Does anyone have any ideas?
Here is the proxy.conf configuration too ProxyPass / h ttp://backend-app-server.company.com/ ProxyPassReverse / h ttp://backend-app-server.company.com/ *NOTE* broke the "http" above to "h ttp" due to restrictions
resolved! headerBufferSize setting in the Jetty app server was set too low. Increasing it worked perfectly.