Re: Tomcat 4.1.18 changes https into httpss
Hello there... I have a web app that works perfect under tomcat 4.1.12. I'm using apache + mod_jk. It works partially ok with 4.1.18, everything under http works fine, but if i call something using https, i get the following error: An error occured while loading https://my.server.com/myapp/secure/activation.jsp: Could not start process Unable to create io-slave: klauncher said: Unknown protocol 'httpss'. So for some reason, even tho i'm requesting https, something appends an extra s making an httpss request? Again, this app works fine in 4.1.12. Does 4.1.18 requires special configuration for apache or mod_jk or server.xml? 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]
Re: Tomcat 4.1.18 changes https into httpss
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]
RE: Tomcat 4.1.18 changes https into httpss
Can't you determine if something is over SSL using ServletRequest.isSecure()? In any case, your filter can still check for 443 regardless of the implementation differences between .12 and .18 using ServletRequest.getServerPort(). Just don't use getRequestURL(). John -Original Message- From: Alexander Wallace [mailto:[EMAIL PROTECTED]] Sent: Monday, January 06, 2003 2:40 PM To: Tomcat Users List Subject: Re: Tomcat 4.1.18 changes https into httpss 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] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.1.18 changes https into httpss
Yeah, I find most problems of it worked on version 4.x, but not 4.y are resolved down to: 1) The app really did change even though the person reporting the problem claims it did not 2) The app is coded around a feature(read: Bug), which has been fixed. :) This has gotten us mostly with respect to differences in handling of UTF strings. 3) configuration changes that are needed by code introduced in the later Tomcat version 4) A real bug introduced in the tomcat code. Usually in that order. In your case, it was a nasty variation on number 2, not something that would be easily findable. Glad to see you tracked it down. - Jeff Tulley [EMAIL PROTECTED] 1/6/03 12:40:19 PM 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! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: NOONE? Was: Tomcat 4.1.18 changes https into httpss
Did you find a similar problem then using apache and apache-ssl with tomcat 4.1.18? What makes me wonder if this is a bug or something is that the same app, with the same settings for mod_jk, works perfectly with TC 4.1.12 and before. I was hopping someone here on the list would tell me if this is normal or i'm messing up in the configuration. If i can't get any other clues on how to make apache-ssl + tc 4.1.18 i may give your hack a go, and will glady accept your offer to help... Thank you very much for your response. On Sunday 05 January 2003 12:21 am, David Orriss Jr wrote: Actually in my case I 'punted' I used ProxyPass and ProxyPassReverse and pass the SSL requests via a URL over to the non-SSL servlet engine... Yea it was a hack, but effective.. ;) On Saturday, January 04, 2003 5:02 PM, Alexander Wallace [EMAIL PROTECTED] wrote: Really noone read my mayl or has any clue as of what am i doing wrong? If it is something that was discussed a lot, i did not see anything in the archives, if so, at least tell me so. I really need help here. -- David Orriss Jr. Please email me if you want my ICQ/AIM/IM ID's. -- 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]
NOONE? Was: Tomcat 4.1.18 changes https into httpss
Really noone read my mayl or has any clue as of what am i doing wrong? If it is something that was discussed a lot, i did not see anything in the archives, if so, at least tell me so. I really need help here. On Friday 03 January 2003 06:41 pm, Alexander Wallace wrote: Hello there... I have a web app that works perfect under tomcat 4.1.12. I'm using apache + mod_jk. It works partially ok with 4.1.18, everything under http works fine, but if i call something using https, i get the following error: An error occured while loading https://my.server.com/myapp/secure/activation.jsp: Could not start process Unable to create io-slave: klauncher said: Unknown protocol 'httpss'. So for some reason, even tho i'm requesting https, something appends an extra s making an httpss request? Again, this app works fine in 4.1.12. Does 4.1.18 requires special configuration for apache or mod_jk or server.xml? Thanks in advance. -- 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]
Anyone? Was: Tomcat 4.1.18 changes https into httpss
Anyone using tomcat 4.1.18 with apache-ssl? On Friday 03 January 2003 06:41 pm, Alexander Wallace wrote: Hello there... I have a web app that works perfect under tomcat 4.1.12. I'm using apache + mod_jk. It works partially ok with 4.1.18, everything under http works fine, but if i call something using https, i get the following error: An error occured while loading https://my.server.com/myapp/secure/activation.jsp: Could not start process Unable to create io-slave: klauncher said: Unknown protocol 'httpss'. So for some reason, even tho i'm requesting https, something appends an extra s making an httpss request? Again, this app works fine in 4.1.12. Does 4.1.18 requires special configuration for apache or mod_jk or server.xml? Thanks in advance. -- 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]
Re: NOONE? Was: Tomcat 4.1.18 changes https into httpss
Actually in my case I 'punted' I used ProxyPass and ProxyPassReverse and pass the SSL requests via a URL over to the non-SSL servlet engine... Yea it was a hack, but effective.. ;) On Saturday, January 04, 2003 5:02 PM, Alexander Wallace [EMAIL PROTECTED] wrote: Really noone read my mayl or has any clue as of what am i doing wrong? If it is something that was discussed a lot, i did not see anything in the archives, if so, at least tell me so. I really need help here. -- David Orriss Jr. Please email me if you want my ICQ/AIM/IM ID's. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: NOONE? Was: Tomcat 4.1.18 changes https into httpss [RBS2003010500002342]
Ahoy there! This is an automated response, to let you know that we have received your query and will answer your email as soon as possible. We know you'd like to get back to playing our state-of-the-art online games. We'd therefore like to assure you that we are determined to keep our service at the level that you've come to expect from The River Belle Online Casino. Thank you for your patience and enjoy your day! Best wishes, Sebastian First Mate RIVER BELLE ONLINE CASINO RIVER BELLE CASINOS ONLINE RIVER BELLE ACES HIGH Enjoy Southern HospitalityFast Paced Casino Action www.riverbelle.com/a3099 www.aceshigh.com/a3181 24/7 toll-free support24/7 toll-free support USA:1 888 615 2383USA:1 877 566 0482 CANADA: 1 888 552 4196CANADA: 1 877 776 0549 UK: 0 800 783 4381UK: 0 800 169 8796 E-mail support: E-mail support [EMAIL PROTECTED][EMAIL PROTECTED] E.O.E. The River Belle Online Casino respects your online time and privacy. If you wish to be removed from our mailing list and not receive any promotional e-mails from us, please send an e-mail to [EMAIL PROTECTED] and type UNSUBSCRIBE in the subject bar. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat 4.1.18 changes https into httpss
Hello there... I have a web app that works perfect under tomcat 4.1.12. I'm using apache + mod_jk. It works partially ok with 4.1.18, everything under http works fine, but if i call something using https, i get the following error: An error occured while loading https://my.server.com/myapp/secure/activation.jsp: Could not start process Unable to create io-slave: klauncher said: Unknown protocol 'httpss'. So for some reason, even tho i'm requesting https, something appends an extra s making an httpss request? Again, this app works fine in 4.1.12. Does 4.1.18 requires special configuration for apache or mod_jk or server.xml? Thanks in advance. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
