Thank you very much for the reply. After double checking all my settings and for hunting where the problem was, i disabled a filter i had implemented to ensure that https was being used when i wanted.
Disabling the filter allowed tc 4.1.18 to work using https. So now the problem becomes why the filter does work under 4.1.12 and not 4.1.18. A quick debug of the filter shows that the problem must be of implementation. Tomcat 4.1.12's httpRequest.getRequestURL() returns http://my.server.com:443/myapp ^^^ That's the only way i had to know if i was being requested something via SSL, so i wrote my filter to check for the secure port. Tomcat 4.1.18's httpRequest.getRequestURL() returns https://my.server.com/myapp ^^^^^ And even though my TC doesn't handle the SSL, i'm now told what scheme is being requested. This is a wellcome change, I just didn't know about it! I hope it stays that way, becouse i now have to rewrite the filter, i hope i don't have to rewrite it again for future upgrades. Any coments? Suggestions? PS. I'm running linux, debian (woody and sid)... jdk 1.4.1-rc-b19. Apache-ssl 1.3.26 Again thanks! > Alexander, > This sounds like a bug to me. If so, instead of moving to a > different "hack" to solve the problem, I think it would be good to fix > it. > What OS are you using, and can you provide any more setup details, how > your SSL is set up, etc.? > This should also probably be brought up on the development mailing > list. > > And, are you 100% sure that the app doesn't change at all and it works > on 4.1.12 and not 4.1.18? > > - Jeff Tulley > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> For additional > commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
