On Tue, Jan 23, 2018 at 1:03 PM, Robert J. Carr <rjc...@gmail.com> wrote:
> On Tue, Jan 23, 2018 at 9:54 AM, Konstantin Kolinko < > knst.koli...@gmail.com> wrote: > >> 2018-01-22 11:25 GMT+03:00 Robert J. Carr <rjc...@gmail.com>: >> > Hi Mark, everyone- >> > >> > I've constructed a sample app of ~5 files. The code is bundled in the >> jar >> > file in the WEB-INF/lib directory. Here's a public url for the >> application >> > (test.war; 8K): >> > >> > >> > https://drive.google.com/file/d/1mZRXrm90F4WN3mizqoqrWYmQ1HH >> frSS4/view?usp=sharing >> > >> >> Thank you for the sample application! It is easy to reproduce the issue. >> >> I filed it into Bugzilla: >> https://bz.apache.org/bugzilla/show_bug.cgi?id=62036 >> >> I went on to upload your test.war there (I fixed some typos in web.xml >> and repacked). I hope that you do not mind. >> >> >> Best regards, >> Konstantin Kolinko >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > Hi Konstantin- > > Thanks for looking into this, and yes, it's fine to share the example > application. > > It looks like you've already done some research. I'll follow the defect > ticket and see what happens. I was hoping there was just some > configuration I was missing, so I'll still hold out for that. > > Thanks again for the time, and a special thanks for confirming I'm not > crazy! :) > > Robert > > Hi Mark, Konstantin- I looked in on that defect ticket and it appears you found and fixed a problem. Great! But I also noticed you said the same problems were happening for you in 8 and 8.5 and even happening in the same version of 8 I was testing against. So I went and grabbed a clean version of 8.0.43 and sure enough, you're right, I'm seeing the same problems there as well. But this is good news, as it means there's a config that can likely fix the problem. I was in the process of writing this long email, hoping you could help me find the config that makes the difference, and *finally* I found it. Turns out if you turn on single sign-on then this bug doesn't present itself. I had forgot I had turned that on in my test server. So, although you fixed the bug, I thought you'd like to have that information. And to say thanks for indirectly helping me to find a solution! Cheers- Robert
