I agree that mod_proxy_ajp is more commonly supported. I've looked/briefly worked on the mod_jk source and it was pretty awful - but that's what happens to code over time. I see your point regarding the ajp protocol but equally, HTTP is everywhere and if every other part of a web stack is HTTP, there seems little value in doing anything different between Apache & Tomcat. AJP has various load balancing features/etc and if that's what one wants, fine, but most organisations have hardware load balancers etc to do this for them now-a-days.
Going back to my request, I note the Servlet Specification API docs state that getRemoteUser should return the CGI variable REMOTE_USER: http://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/http/HttpServletRequest.html#getRemoteUser() But as I've highlighted, it does not, so Tomcat is in breach of the spec. How can this be raised as a bug? On Fri, Jul 24, 2015, at 09:39 AM, S.Booth wrote: > On 23/07/15 20:38, John Baker wrote: > > The flag to which you refer is for AJP only, hence the inconsistency (as > > AJP becomes less common and reverse proxying HTTP becomes the norm). > > While I agree with you that the http connector should be consistent with > the AJP behavior where possible I'm interested if you think reverse > proxy http is better for any reason. I switched to mod_proxy_ajp from > mod_jk because it seemed more commonly supported out of the box but I > never saw any reason to give up on ajp. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
