[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re: SSL problem + Apache 1.3.33



On Fri, Aug 19, 2005 at 11:45:36AM +0200, Belikov Anton wrote:
> 
> Hi All,
> I have the same problem with Apache 2 / mod_ssl under Red Hat. Can you please give me a hint. What was the reason in this case? I also can use http://myserver:443 while https://myserver doesn't work and  I see in access_log
> 10.10.10.99 - - [19/Aug/2005:11:39:38 +0200] "?L?????????" 501 405 "-" "-"
> 10.10.10.99 - - [19/Aug/2005:11:39:38 +0200] "?L?????????" 501 405 "-" "-"
> In error log 
> [Fri Aug 19 11:39:38 2005] [error] [client 10.10.10.99] Invalid method in request ?L?????????
> [Fri Aug 19 11:39:38 2005] [error] [client 10.10.10.99] Invalid method in request ?L?????????

I suppose you're referring to this old thread
http://lists.debian.org/debian-user/2005/04/msg00274.html

The original poster back then had two IP-based virtual host sections
for the same IP address, the first without a port specification, the
second with :443.

In my final reply in this thread I suggested to explicitly specify the
non-SSL port, too, i.e.:

  <VirtualHost IPaddress:80>
                        ^^^
    ... HTTP setup ...

  </VirtualHost>

  <VirtualHost IPaddress:443>

    ... HTTPS setup ...

  </VirtualHost>

the idea being that, in case the virtual host IP without port would
match _both_ ports, it might inadvertendly cause requests on 443 be
routed to the wrong virtual host section) -- in particular, as the
HTTP section appeared first (the order is important, when things are
ambiguous).

Unfortunately, I can't tell for sure whether that worked[1], because
I didn't get any feedback form the original poster.  So, if _you_
eventually do solve the issue, _please_ report back on-list to let
other people benefit, who will google this up in the future.
Apparently, this problem occurs rather frequently (during the last
couple of months I got five (!) related inquiries off-list...).

HTH,
Almut

[1] I was able to reproduce the problem myself with a similar config
(without :80 on the first virtual host), when additionally _not_
specifying the "Port 80" directive (i.e. only having "Listen 80" and
"Listen 443").



Reply to: