https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #18 from xudong.liu ---
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.
---
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #17 from saurabh ---
(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 identical steps th
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #16 from Christopher Schultz ---
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 Java SSL layer is so far below
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #15 from Mark Thomas ---
(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 this. Instead
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #14 from Konstantin Preißer ---
(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 browser receives
>
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #13 from robchek ---
(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)
> - connecting to the https port
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #12 from saurabh ---
Created attachment 30912
--> https://issues.apache.org/bugzilla/attachment.cgi?id=30912&action=edit
HTTP 0.9 response from the server
I tried the identical steps that have been provided and the browser re
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
Mark Thomas changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #10 from Christopher Schultz ---
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 password:
What is your firs
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
robc...@knowledgetree.com changed:
What|Removed |Added
CC||robc...@knowledgetree.co
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
robc...@knowledgetree.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolu
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
Konstantin Kolinko changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|-
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
Bruce Li changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #6 from Christopher Schultz ---
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
circumstances: httpd is an example of how
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #5 from saurabh ---
@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 Configuration ?
--
You are
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #4 from Christopher Schultz ---
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, Tomcat certainly can't do it usi
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #3 from saurabh ---
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.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
--- Comment #2 from Christopher Schultz ---
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 my.secure.site.com.
Escape character is '^]'.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=53281
saurabh changed:
What|Removed |Added
CC||saurabhsul...@yahoo.co.in
--
You are re
20 matches
Mail list logo
