>
> Can't you just add a custom response header to your Tomcat responses like
>
> X-REMOTE-USER: MY_USER
>
> and then log the user name in your apache access log by adding
> %{X-REMOTE-USER}o?
Hi,
Yes, this is what Konstantin suggests. I guess I will drop my initial idea and
follow this rou
> 3. You would need some additional work and configuration on httpd side
> to make the information provided by Tomcat be printed into the logs.
[1] Isn't it possible for to set the user for the current request in httpd
context via mod_jk ? I guess this would be half good, as this info would only
On 23.03.2012 13:43, issa.goris...@ext.ec.europa.eu wrote:
Hi All,
I have several web applications running on distinct tomcat instances. Apache
httpd is in front of all the tomcat instances, running as a reverse proxy.
Authentication is realized at the container side. Access log files are acti
2012/3/23 :
>>
>> That works only if authentication is done by Tomcat. In many cases
>> authentication is done by 3-rd party frameworks e.g. Spring Security,
>> inside the web application itself.
>>
>> I think patching the connectors and mod_jk is not a good idea here.
>>
>
>
> Well, I have indee
> > I have several web applications running on distinct tomcat instances.
> Apache httpd is in front of all the tomcat instances, running as a reverse
> proxy. Authentication is realized at the container side. Access log files are
> active on the httpd side.
>
> "at the container side" = in Tomcat
2012/3/23 :
> Hi All,
>
> I have several web applications running on distinct tomcat instances. Apache
> httpd is in front of all the tomcat instances, running as a reverse proxy.
> Authentication is realized at the container side. Access log files are active
> on the httpd side.
"at the conta
