[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2014-07-14 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #18 from xudong.liu xu-dong@sap.com --- I meet the same issue in my test. I want to know if this issue can be fixed? Why it's status is marked invalid? -- You are receiving this mail because: You are the assignee for the

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-10 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #17 from saurabh saurabhsul...@yahoo.co.in --- (In reply to Konstantin Preißer from comment #14) (In reply to saurabh from comment #12) Created attachment 30912 [details] HTTP 0.9 response from the server I tried the

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #12 from saurabh saurabhsul...@yahoo.co.in --- Created attachment 30912 -- https://issues.apache.org/bugzilla/attachment.cgi?id=30912action=edit HTTP 0.9 response from the server I tried the identical steps that have been

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #13 from robchek robc...@knowledgetree.com --- (In reply to Mark Thomas from comment #11) Tested with 6.0.x and confirmed that: - connecting to the https port using http with a browser returns garbage (as expected) -

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #14 from Konstantin Preißer kpreis...@apache.org --- (In reply to saurabh from comment #12) Created attachment 30912 [details] HTTP 0.9 response from the server I tried the identical steps that have been provided and the

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #15 from Mark Thomas ma...@apache.org --- (In reply to Konstantin Preißer from comment #14) As you can see, Tomcat didn't returin anything like HTTP/0.9 200 OK plain text in its SSL response although Live HTTP Headers reports

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #16 from Christopher Schultz ch...@christopherschultz.net --- Mark, can you comment on why Tomcat is limited further than, say, httpd? I think that might help drive the final nail in the coffin, here. Is the problem that the

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 robc...@knowledgetree.com changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 robc...@knowledgetree.com changed: What|Removed |Added CC|

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #10 from Christopher Schultz ch...@christopherschultz.net --- Note that I tested this with Tomcat 8 trunk. $ keytool -genkey -alias tomcat -keystore ~/.keystore -keyalg RSA -keysize 4096 Enter keystore password: Re-enter new

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2013-10-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-12-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Bruce Li wbing...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-12-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Konstantin Kolinko knst.koli...@gmail.com changed: What|Removed |Added Status|REOPENED

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-06-06 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #4 from Christopher Schultz ch...@christopherschultz.net --- My question isn't whether Tomcat can be configured to do that (it cannot currently do it), but if JSSE will even allow that handling to occur. If JSSE can't do it,

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-06-06 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #5 from saurabh saurabhsul...@yahoo.co.in --- @Christopher Schultz - So if I understand you correctly, the issues lies with JSSE and not Tomcat, may I right? And that, there is no way we can change the behavior using Tomcat

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-06-06 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #6 from Christopher Schultz ch...@christopherschultz.net --- No, I'm not saying that the issue is JSSE (though it may be). What I'm saying is that responding to an HTTP request over HTTPS is not impossible under all

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-06-05 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #2 from Christopher Schultz ch...@christopherschultz.net --- Apache httpd does do something like this; not sure if it's possible using JSSE: $ telnet my.secure.site.com 443 Trying 208.85.173.131... Connected to

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-06-05 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 --- Comment #3 from saurabh saurabhsul...@yahoo.co.in --- Yes, Apache httpd does that. But I haven't been able to produce the same behavior using JSSE in Apache Tomcat. -- You are receiving this mail because: You are the assignee for the

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-06-03 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 53281] Tomcat returns garbage data with HTTP/0.9 200 OK header when SSL port is accessed using http

2012-05-23 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281 saurabh saurabhsul...@yahoo.co.in changed: What|Removed |Added CC|