ajp

I understand that configured attributes will be stored as environment variables by default and will be accessible like request.getAttribute("Shib-Identity-Provider") I tried that and after some googling I understood that to access them in Java through AJP. I need to prefix this <ApplicationDefaults id="default" policyId="default" entityID="https://idp.example.org" REMOTE_USER="eppn persistent-id targeted-id" signing="false" encryption="false" attributePrefix="AJP_"> I did that but I still keep getting null in my Java application Shib-Identity-Provider - null Shib-Session-ID - null Shib

If you're not using AJP, Tomcat 6.0 Connectors have a nice maxHttpHeaderSize attribute in server.xml . But if you are using AJP, that attribute is not understood. Is there any way to increase the allowed HTTP header size if you are writing an app that is using AJP? ( maxHttpHeaderSize is documented at http://tomcat.apache.org/tomcat-6.0-doc/config/http.html but there is also this in that document: "If you wish to configure the Connector that is used for connections to web servers using the AJP protocol (such as the mod_jk 1.2.x connector for Apache 1.3), see here instead." The "here" link

I've been trying to configure Apache web server with a Spring Boot app that uses embedded Tomcat. Before Spring Boot I used to create an ajp.conf file like: <VirtualHost *:80> ServerName localhost <Proxy *> AddDefaultCharset Off Order deny,allow Allow from all </Proxy> ProxyPass /app ajp://localhost:8009/app ProxyPassReverse /app ajp://localhost:8009/app </VirtualHost> And include in the httpd.conf file like Include /opt/lampp/apache2/conf/ajp.conf And in the Tomcat's server.xml file, I used to configure it to listen to port 8009 <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"

This error has been driving me nuts. We have a server running Apache and Tomcat, serving multiple different sites. Normally the server runs fine, but sometimes an error happens where people are served the wrong page - the page that somebody else requested! Clues: The pages being delivered are those that another user requested recently, and are otherwise delivered correctly. It's been known for two simultaneous requests to be swapped. As far as I can tell, none of the pages being incorrectly delivered are older than a few minutes. It only affects the files that are being served by Tomcat.

Is there any way I connect Apache to Tomcat using an HTTP proxy such that Tomcat gets the correct incoming host name rather than localhost? I'm using this directive in apache: ProxyPass /path http://localhost:8080/path But it comes through as localhost, which is useless when we have a bunch of sites on the same server. I could set the host manually in the server config: <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" proxyName="pretend.host" proxyPort="80" /> But that again doesn't serve more than one site. And I don't like the idea of using a different internal port for