Thanks Chuck.
It is clear that I am still a little behind the times.
Regards,
Andrew
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, 14 December 2006 1:23 PM
To: Tomcat Users List
Subject: RE: strange ssl tomcat response
> From: Andrew Frie
Yes, trying this (http://localhost:8443) with FF results in a prompt to
download a BIN file, which turns out to be:
prompt> od -a ldlepaov\(2\).bin
000 nak etx soh nul stx stx nl
007
I'll leave interpretation of the "correctness" of that to you :-)
--
Hassan Schroeder -
On 12/14/06, Martin Heiden <[EMAIL PROTECTED]> wrote:
It's pretty valid!
I don't think so.Just checked out the TLS rfc and found this (TLS ver. 1.0):
These goals are achieved by the handshake protocol, which can be
summarized as follows: The client sends a client hello message to
which t
Hi!
> http://localhost:8443 (note the http not the https)
> I am pretty sure that this is NOT valid behaviour.
Why do you think so? I that tomcat will initialise the SSL
negotiation. Client and Server have to exchange the keys. If you do
not tell the browser that it has to do this negotiation (yo
I have did yet another try,now on windows machine .
The same problem!
Here are the steps to reproduce :
[1] Do a regular (vanilla) installation of tomcat (Linux and Windows i have
already tried) .
[2] Setup ssl:
Uncomment the ssl setup in server.xml create a key with the following:
%JAVA_HOME%\bin
> From: Andrew Friebel [mailto:[EMAIL PROTECTED]
> Subject: RE: strange ssl tomcat response
>
> This is going to seem like a dumb question, but are you
> running the SDK or RTE with tomcat? You need to be
> running the SDK.
Your information is out of date, as a cursory lo
,
Andrew
-Original Message-
From: Hassan Schroeder [mailto:[EMAIL PROTECTED]
Sent: Thursday, 14 December 2006 7:38 AM
To: Tomcat Users List
Subject: Re: strange ssl tomcat response
On 12/13/06, Tsirkin Evgeny <[EMAIL PROTECTED]> wrote:
> tomcat 5.5.20
I remembered I had a vanill
On 12/13/06, Tsirkin Evgeny <[EMAIL PROTECTED]> wrote:
tomcat 5.5.20
I remembered I had a vanilla install of 5.5.20 not yet in use, so I
uncommented the https connector and created a keystore
java version "1.5.0_09"
/me == 1.5.0_06 on this machine
Linux SuSe
/me == SuSE 10.0
So, pretty clo
ponse with strange bits when telneting to the ssl port.
Anybody please?
Evgeny.
On 12/13/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: Tsirkin Evgeny [mailto:[EMAIL PROTECTED]
> Subject: Re: strange ssl tomcat response
>
> How do i check for an APR existens ?
Since
> From: Tsirkin Evgeny [mailto:[EMAIL PROTECTED]
> Subject: Re: strange ssl tomcat response
>
> How do i check for an APR existens ?
Since this is a Linux box and you did not explicitly build and install
it, it's extremely unlikely that you have it.
- Chuck
THIS COMMUNIC
On 12/13/06, Tsirkin Evgeny <[EMAIL PROTECTED]> wrote:
when connecting via telnet i am first getting an empty response
typing in some character and only then i am getting the bits.
The strange response bits are what i got here just befor "Connection
closed".
No, if I enter something aft
Hassan ,just a thought:
when connecting via telnet i am first getting an empty response
typing in some character and only then i am getting the bits.
Is that what you tried?
-
telnet localhost 8443
Trying 127.0.0.1...
Connected to localhost.
Esca
On TLS i am getting the same result.
How do i check for an APR existens ?
Chuck suggested that this is the problem.
However I don't know where to look .
I am using 5.5.20 could that be a problem?
Thanks.
Evgeny.
On 12/13/06, Hassan Schroeder <[EMAIL PROTECTED]> wrote:
On 12/13/06, Tsirkin Evgen
On 12/13/06, Tsirkin Evgeny <[EMAIL PROTECTED]> wrote:
Basically that can be checked in a very simple manner:
try to setup ssl for a tomcat and then telnet to it (8443 port).
Do you get any response?
Just tried on a 5.5.9 non-APR system -- no response :-)
[1] If no that is problem in my conf
I don't expect it to work .
I expect to return either 404 , 500 http status (maybe any other) or nothing
.
try this:
telnet mail.google.com 443
You will get a connection however NOTHING will be returned .
Now ,I am trying ssl connection to tomcat :
telnet myhost 8443
And getting the strange bits.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evgeny,
Tsirkin Evgeny wrote:
> I have setted up a tomcat to listen to ssl on 8443 port. When i use
> url https://myhost:8443/ everything works fine.
>
> However when pointing my browser to http://myhost:8443/ I am getting
> strange response.
What d
will know for sure.
Thanks for the answer!
Hope you will be able to help me.
Evgeny.
On 12/13/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: Tsirkin Evgeny [mailto:[EMAIL PROTECTED]
> Subject: strange ssl tomcat response
>
> Hope this will not be posted twice.
My
> From: Tsirkin Evgeny [mailto:[EMAIL PROTECTED]
> Subject: strange ssl tomcat response
>
> Hope this will not be posted twice.
If you don't provide basic information, it will have to be.
1) What version of Tomcat?
2) What JVM (vendor and level)?
3) What OS?
4) Do you have APR
Hi list!
Hope this will not be posted twice.
I have setted up a tomcat to listen to ssl
on 8443 port.
When i use url https://myhost:8443/ everything works fine.
However when pointing my browser to
http://myhost:8443/
I am getting strange response .
It looks something like this in text representati
19 matches
Mail list logo
