Am So, den 04.01.2004 schrieb Ron Peters um 01:34: > > Am So, den 04.01.2004 schrieb Ron Peters um 00:51: > > > > [ snip ] > > > >> Ok, I've done these steps and was able to get the server restarted > >> without > >> errors. But now, when I go to https://myserver.com, I get this popup > >> message: The connection to myserver.com has terminated unexpectedly. > >> Some > >> data may have been transferred. > >> > >> I see no errors in any httpd log. If I telnet to myserver 443, I get > >> this: > >> > Trying again with correct syntax: > > Trying 172.16.5.4... > Connected to myserver.com. > Escape character is '^]'. > GET duh.html HTTP/1.0 (yes, duh.html does exist) > > HTTP/1.1 400 Bad Request > Date: Sun, 04 Jan 2004 00:25:15 GMT > Server: Apache/2.0.47 (Fedora) > Content-Length: 310 > Connection: close > Content-Type: text/html; charset=iso-8859-1 > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>400 Bad Request</title> > </head><body> > <h1>Bad Request</h1> > <p>Your browser sent a request that this server could not understand.<br /> > </p> > <hr /> > <address>Apache/2.0.47 (Fedora) Server at www.myserver.com Port 443</address> > </body></html> > Connection closed by foreign host. > > The above does generate an entry in the myserver.com-error.log file like > this: > > [Sat Jan 03 16:25:15 2004] [error] [client 172.16.5.2] Invalid URI in > request GET duh.html HTTP/1.0 > > I guess the error returned is becaue I added 2 carriage returns. If I > don't put two in, the server just doesn't respond with anything. > > > > > There are: > > /var/log/httpd/ssl_access_log > > /var/log/httpd/ssl_error_log > > Especially the error log file should contain relating data for > > debugging. > > These log files aren't reporting anything at all. > > > > > Does "apachectl -t" and "apachectl -S" report both OK? > > These both return "Syntax OK" > > > > > Alexander > > > > Anything else? > Ron. Strange. I just noticed that certainly it is not possible to get a valid response from HTTPS by using telnet to port 443. But if it would work on your side, your server should have responsed different than posted by you. You did install the httpd rpm and mod_ssl? Made you own self-signed certificate/key? What do you get when you try to access your SSL apache site by using a browser? If you did not something corious HTTPS would work by default without any needed changes. Maybe you should reset your ssl.conf settings back to default, especially the certificate/key entries. Alexander -- Alexander Dalloz | Enger, Germany PGP key valid: made 13.07.1999 PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
