Re: AW: JSessionId secure attribute not set if RemoteIpFilter with X-Forwarded-Proto https is used

Hi Reto, fortunately I use RemoteIpValve but I would like to know, if you have time, what advantages there would be using RemoteIpFilter. TIA Il 09/02/2023 08:50, Reto Weiss ha scritto: Hi Mark Reported ashttps://bz.apache.org/bugzilla/show_bug.cgi?id=66471 Regards Reto

AW: JSessionId secure attribute not set if RemoteIpFilter with X-Forwarded-Proto https is used

Hi Mark Reported as https://bz.apache.org/bugzilla/show_bug.cgi?id=66471 Regards Reto - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org

Re: JSessionId secure attribute not set if RemoteIpFilter with X-Forwarded-Proto https is used

On 08/02/2023 12:26, Reto Weiss wrote: Hi There I use Tomcat 9.0.68 and the org.apache.catalina.filters.RemoteIpFilter**Filter behind a NGINX reverse proxy. On the NGINX I set the http header X-Forwarded-Proto to https. If I now make a request with a Browser to the reverse proxy the

JSessionId secure attribute not set if RemoteIpFilter with X-Forwarded-Proto https is used

Hi There I use Tomcat 9.0.68 and the org.apache.catalina.filters.RemoteIpFilter Filter behind a NGINX reverse proxy. On the NGINX I set the http header X-Forwarded-Proto to https. If I now make a request with a Browser to the reverse proxy the JSESSIONID cookie I get back is missing the secure