The interchange also had no effect. Nor did changing the line to:
This doesn't work for me either with or without the trailing slash. I'll try it with the name and alias lines interchanged.
Try it like this. This is mine except my server name and server alias are reversed.
<VirtualHost *:80> </VirtualHost>
I tried adding trailing slashes as follows, but the result was the same: a 111 error. Did I misinterpret your comment?
# http redirect <VirtualHost aaa.bbb.ccc.ddd:80> </VirtualHost>
<Virtualhost *:80> </VirtualHost>
# https versions <VirtualHost aaa.bbb.ccc.ddd:443> ServerAdmin . . . ServerAlias . . . . . .
The (111) is a networking issue because you're not matching the trailing slashes with your redirects. Can you reproduce the issue and provide some logs, and maybe more information about the actual response? the 1xx range isn't supposed to be an error code in HTTP.
I have the following configuration file covering two virtual hosts:
# http redirect <VirtualHost aaa.bbb.ccc.ddd:80> </VirtualHost>
<Virtualhost *:80> </VirtualHost>
# https versions <VirtualHost aaa.bbb.ccc.ddd:443> ServerAdmin . . . ServerAlias . . . . . .
The https parts work well but if people try to get http://host1.com or http://host2.com they get connection (111) errors indicating that the redirects aren't working. I've tried different versions of the redirects -- with and without double quotes -- and it doesn't seem to make a difference.
How to I get the redirects to function?
--
Jonathon Koyle
|
