Hi Kem,
Kem Elbrader wrote:
>Looks like I'm not allowed to reopen the issue myself. Can someone
>who does have permission verify that the bug still exists and then
>reopen the issue if so. This seems to be a very critical issue as it
>would prevent Glassfish V2 from being a viable option when using
>Grizzly.
>
>On 8/3/07, Kem Elbrader <kem.elbrader_at_gmail.com> wrote:
>
>
>>I'm still experiencing SSL blocking issue reported on Glassfish issue 1710.
>>I get the same problem on both b57 and b50g.
>>
>>https://glassfish.dev.java.net/issues/show_bug.cgi?id=1710
>>
>>Use telnet to block the connection
>>telnet localhost 8181
>>
>>Is anyone else getting this? I wanted to make sure here before I
>>reopened the issue.
>>
>>
I'm not sure I'm able to reproduce the issue.
Here's what I did:
1. telnet localhost <https-port>
2. In parallel, access
https://localhost:<https-port>/ from browser
In 2., I was prompted to inspect the server's SSL cert, and after
accepting it,
the server's index.html page was served, as expected.
I've tried this with the https listener's "blocking-enabled" attribute
set to
"true", and tried it again after restarting the server with this
attribute set to
"false". Either case worked fine for me.
I've tried this with GlassFish v2 b57 on Solaris.
Can you tell me if I've missed any steps in trying to reproduce the issue?
Thanks,
Jan
>
>