Re: SSL problem + Apache 1.3.33
netstat -tan | grep 443 gives me the following:
tcp 0 0 0.0.0.0:443 0.0.0.0:*
LISTEN
access log each time that I am trying to access the https gives me the
following:
myip - - [03/Apr/2005:21:25:51 +0100] "\x80g\x01\x03\x01" 501 - "-" "-"
"-"
myip - - [03/Apr/2005:21:25:52 +0100] "\x80g\x01\x03" 501 - "-" "-" "-"
myip - - [03/Apr/2005:21:25:55 +0100] "\x80g\x01\x03" 501 - "-" "-" "-"
myip - - [03/Apr/2005:21:26:49 +0100] "\x80g\x01\x03" 501 - "-" "-" "-"
Don't have a clue what the above are...
Error log also gives the following:
[Sun Apr 3 21:25:51 2005] [error] [client myip] Invalid method in
request \\x80g\\x01\\x03\\x01
[Sun Apr 3 21:25:52 2005] [error] [client myip] Invalid method in
request \\x80g\\x01\\x03
[Sun Apr 3 21:25:55 2005] [error] [client myip] Invalid method in
request \\x80g\\x01\\x03
[Sun Apr 3 21:26:49 2005] [error] [client myip] Invalid method in
request \\x80g\\x01\\x03
which also don't have a clue what it might be :)
Where can I set the ssl_engine_log to trace or debug?
I add in my virtualhost the following:
SSLLog /var/log/apache/custom_ssl.log
but the above log does not include anything (restart syslog as well).
Any help is much appretiate.
Thanks
On Sun, 2005-04-03 at 20:17 +0200, Almut Behrens wrote:
> On Sun, Apr 03, 2005 at 06:39:29PM +0100, Stelios A. wrote:
> > No errors related with ssl under apache logs.
> > port 443 is open in firewall and set up correctly under httpd.conf
> > (Listen)
>
> So, do I understand you correctly that you've verified the request does
> in fact reach the server and gets processed at all? (You should at
> least see an entry in access_log, and a whole bunch of messages in
> ssl_engine_log (if you set it to 'trace' or 'debug'[1]).
>
> If so, could you post the relevant section of ssl_engine_log?
>
> If not, have you verified that the server is _if fact_ listening on 443?
> (netstat -tan | grep 443) I know, you have it configured in
> httpd.conf, but who knows what might be going on...? :)
>
> Almut
>
>
> [1] I'm not entirely sure whether 'debug' will actually give you more
> verbose output -- I dimly remember that the code might need to have
> been built with DEBUG option for that to take effect... haven't tried
> right now. If 'debug' does work, you should even get every single byte
> logged, that's being exchanged between client and server.
>
>
Reply to: