It was not the ;jsessionidxx, but changes to Spring StrictHttpFirewall, the
default config now does not allow some characters in the url :
- Rejects URLs that are not normalized to avoid bypassing security
constraints...
- Rejects URLs that contain characters that are not printable ASCII
Hi Greg
-Original Message-
From: Greg Huber [mailto:gregh3...@gmail.com]
Sent: Thursday, April 26, 2018 4:53 AM
To: Tomcat Users List
Subject: Tomcat 9 ;jsessionid
> Hello,
>
> One thing I have noticed with Tomcat 9.0.x I get alot
> ;jsessionid=xxx appended to my urls. This did not hap
Chris,
>As for your image URLs failing due to those path parameters... why are
>they failing? Which component is generating those HTTP 500 responses?
I did some more investigation and my app would not display the image with
the ;
http://www.myapp.co.uk/images/image_32x32.png;jsessionid=52FC7E2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg,
On 4/26/18 4:53 AM, Greg Huber wrote:
> Hello,
>
> One thing I have noticed with Tomcat 9.0.x I get alot
> ;jsessionid=xxx appended to my urls. This did not happen with
> 8.5.x.
>
> /images/image_32x32.png;jsessionid=BF27C604B287CCF6DF3DBDB
On 26/04/18 09:53, Greg Huber wrote:
> Hello,
>
> One thing I have noticed with Tomcat 9.0.x I get alot ;jsessionid=xxx
> appended to my urls. This did not happen with 8.5.x.
>
> /images/image_32x32.png;jsessionid=BF27C604B287CCF6DF3DBDB180C2CBEB
>
> 500 Internal Server Error
>/image
