Dear Wiki user, You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.
The following page has been changed by megaspaz: http://wiki.apache.org/httpd/InvalidMethodHTTPSonHTTP The comment on the change is: fixer upper. ------------------------------------------------------------------------------ ServerName myserver.foo.com DocumentRoot /var/www/myserver - # Missing SSLEngine On + # Missing SSLEngine On and other SSL configuration directives. ... </VirtualHost> }}} - This is not an SSL enabled vhost. This vhost can only be accessed by the user via HTTP - ''http://myserver.foo.com:443''. + This is not an SSL enabled vhost. This vhost can only be accessed by the user via HTTP - ''http://myserver.foo.com:443''. Also, one does not usually use name based vhosts for HTTPS configuration even though it's seen commonly in Debian and Ubuntu tutorials. See the [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts2 official Apache docs] for more information why. '''Or, another example, if your vhosts looke like this:''' @@ -43, +43 @@ </VirtualHost> }}} - Apache will always bypass the SSL vhost because of the * interface/port configuration of your HTTP vhost. You will know this is the cause as when you start Apache, you'll see the [http://wiki.apache.org/httpd/VirtualHostsMixingPorts mixing * ports and non-* ports warning]. This is a common name based vhost configuration mistake. + Apache will always bypass the SSL vhost because of the '''*''' interface/port configuration of your HTTP vhost. You will know this is the cause as when you start Apache, you'll see the [http://wiki.apache.org/httpd/VirtualHostsMixingPorts mixing * ports and non-* ports warning]. This is a common name based vhost configuration mistake. The final scenario would be that you are trying to access a HTTP vhost via HTTPS or vice versa. This does not necessarily mean an Apache misconfiguration on your part. Only that you (or your users) are trying to access a HTTP vhost via HTTPS or a HTTPS vhost via HTTP. - Also note that starting from Apache 2.2, the classic, monolithic httpd.conf file has been broken up into smaller configuration files. One of these being httpd-ssl.conf in the '''conf/extras''' directory. This file contains an SSL vhost configuration along with SSL configuration directives. If you are aware of this file and have made your configurations in this file, make sure that the include line in httpd.conf has been uncommented. + Also note that starting from Apache 2.2, the classic, monolithic httpd.conf file has been broken up into smaller configuration files. One of these is '''httpd-ssl.conf''' in the '''conf/extras''' directory. This file contains an SSL vhost configuration along with SSL configuration directives. If you are aware of this file and have made your configurations in this file, make sure that the include line in httpd.conf has been uncommented. {{{ # Make sure you uncomment the line below!
