Re: 400 error when upgrading tomcat

2020-09-10 Thread Mark Thomas
On 10/09/2020 21:23, Brian Harris wrote: > Thanks Christopher. You just nailed it buddy. I changed them all to \r\n > and it got a 200. I was completely overlooking that as it had never caused > a problem before. Something in 8.5.51 would not allow that anymore. That is the fix for

Re: 400 error when upgrading tomcat

2020-09-10 Thread Brian Harris
Thanks Christopher. You just nailed it buddy. I changed them all to \r\n and it got a 200. I was completely overlooking that as it had never caused a problem before. Something in 8.5.51 would not allow that anymore. On Thu, Sep 10, 2020 at 4:07 PM Christopher Schultz <

Re: 400 error when upgrading tomcat

2020-09-10 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Brian, On 9/10/20 13:13, Brian Harris wrote: > We’re having an issue when upgrading Tomcat from 8.5.50 to 8.5.51. > Since moving to this version, requests sent to the http port are > failing with a 400 error code(bad request). The server.xml is >

400 error when upgrading tomcat

2020-09-10 Thread Brian Harris
We’re having an issue when upgrading Tomcat from 8.5.50 to 8.5.51. Since moving to this version, requests sent to the http port are failing with a 400 error code(bad request). The server.xml is configured to redirect the http port to the https port. This has worked for years and did not start