понедельник, 25 октября 2010 г.

Apache2 Invalid method in request \x16\x03\x01

You are testing your SSL certificate on port 443 and your browser displays this message:
Invalid method in request \x16\x03\x01

You may also see SSL_ERROR_RX_RECORD_TOO_LONG or "www.example.com has sent an incorrect or unexpected message. Error Code: -12263".
You can try debugging the problem by telnetting to the server on port 443 and issuing a GET command:
# telnet 443
Connected to
Escape character is '^]'.

If you get back HTML then you know your server is speaking unencrypted HTTP on port 443, which is bad.
This error is due to a misconfiguration of VirtualHost with SSL. The server is trying to respond to a request on port 443 with unencrypted HTTP. In other words, your browser is expecting SSL, but the server is sending plain HTTP on port 443.
Typically your conf/httpd.conf file will include conf/extra/httpd-ssl.conf:
Include conf/extra/httpd-ssl.conf

The default httpd-ssl.conf file will have a section like this:


Almost certainly the problem is that your server is using this default or the server is not matching your virtual host's IP at all. For SSL to work you must match the virtual host by IP address not name.

could not bind to address

If you get this error on startup then it means that you have a configuration problem where the server is trying to listen on all interfaces on port 443 and you have told it to listen to port 443 on a specific interface.
Address already in use: make_sock: could not bind to address

Probably you have a section with a specific VirtualHost IP address conflicting with the _default_ VirtualHost. A section something like this "" cannot be used with the default section like this "".

Комментариев нет: