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

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

to handle this correct. Also, the secure flag can be enforced by setting it in the web.xml. However, I would like to use RemoteIpFilter because it has some advantages over the RemoteIpValve or statically setting it in the web.xml. Should I file an issue for this? Regards Reto Weiss El. Ing. HTL