Randal,
Thanks for the tip. So my question is: what is the best solution? I want
to redirect http://cloudstock.com/ to http://www.cloudstock.com/.
Should I take out the permanent in the Redirect directive? Should the
www entry come first? Do I need to get another IP address?
Or do you know what bit of cookie magic I need to get the cookies to
stick to cloudstock.com? I have implemented it for now anyway. Once I
figure something else out or start getting complaints I'll change it.
"Randal L. Schwartz" wrote:
>
> >>>>> "Rusty" == Rusty Foster <[EMAIL PROTECTED]> writes:
>
> Rusty> NameVirtualHost 216.181.35.174 # IP of www.kuro5hin.org
>
> Rusty> # Redirect all hostless requests to www VHost
> Rusty> <VirtualHost 216.181.35.174>
> Rusty> ServerName kuro5hin.org
> Rusty> Redirect permanent / http://www.kuro5hin.org/
> Rusty> </VirtualHost>
>
> Rusty> # Proper URI for www.kuro5hin.org
> Rusty> <VirtualHost 216.181.35.174>
> Rusty> ServerName www.kuro5hin.org
> Rusty> ...etc...
> Rusty> </VirtualHost>
>
> Rusty> This way, people who come in to http://kuro5hin.org/ get redirected
> Rusty> right off the bat, and so far this seems to have solved the problem.
>
> Except that this requires HTTP/1.1. Anyone that doesn't send the
> "host:" header goes into a permanent redirect loop. So the "problems"
> you're not seeing are probably from the people out there that can't
> get to your site to report the problems. :)
--
Drew Taylor
Vialogix Communications, Inc.
501 N. College Street
Charlotte, NC 28202
704.370.0550
http://www.vialogix.com
