[Bug 59317] AsyncContextImpl breaks request URL containing spaces

https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 --- Comment #7 from Mark Thomas --- Potential regressions should be followed up on the users list in the first instance and be accompanied by simple test cases (JSPs can be useful for this) that demonstrate the problem. That

[Bug 59317] AsyncContextImpl breaks request URL containing spaces

https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 --- Comment #6 from Nitin Kamate --- The change done for this issue caused regression in the webapp and We wan into this of URL encoding. Few of the URLs that use : inside are getting encoded and the server is unable to

[Bug 59317] AsyncContextImpl breaks request URL containing spaces

https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 --- Comment #5 from seandawson2...@gmail.com --- So we ran into this too - with a customer who downloaded the latest rev of Tomcat 8. Took us half the day yesterday and most of today to get to the bottom of it. In troubleshooting, I tried

[Bug 59317] AsyncContextImpl breaks request URL containing spaces

https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 --- Comment #4 from Vincent Massol --- Hi, I believe this issue and the change brought with it are causing regressions in apps using Tomcat (such as XWiki). See http://markmail.org/message/jwm5ip245empcghi Do you think

[Bug 59317] AsyncContextImpl breaks request URL containing spaces

https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 59317] AsyncContextImpl breaks request URL containing spaces

https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 --- Comment #2 from Mark Thomas --- A few more notes as I investigate this. Async and non-async behaviours are currently the same. - Both expect the path used to obtain the dispatcher to be decoded. This behavior was

[Bug 59317] AsyncContextImpl breaks request URL containing spaces

https://bz.apache.org/bugzilla/show_bug.cgi?id=59317 --- Comment #1 from Mark Thomas --- See also bug 57559. I'm close to marking this bug as a duplicate of that one but I do want to review the detail of exactly what is going on first. -- You are receiving this mail because: