|
|
Posted by Rik on 03/06/07 05:43
Vic Spainhower <vic@showsec.com> wrote:
>>>> www.example.com is not the same as example.com. It may or may not =
be =
>>>> on
>>>> the same server. And if it were on a different server, there could=
=
>>>> be a
>>>> security exposure.
>>>>
>>> It is always the same domain. What server hardware is used is =
>>> irrelevant.
>>> An HTML request for www.thisdoman.com will always produce the same
>>> resulting connection as thisdomain.com.
No it will not, and I'm amazed you dare to state such a huge error as an=
=
absolute truth.
> I placed the following re-direct in index.php and it goes into a =
> re-direct
> loop. This would tell me they are in fact the same domain and a re-dir=
ect
> will not solve the problem.
>
> <meta http-equiv=3D"REFRESH" content=3D"2; =
> URL=3Dhttp://www.mysite.com">
You have to check wether they're at the right domain offcourse. If it =
resolves to the same directory, I'd either make _all_ links relative, or=
=
I'd use mod_rewrite in apache for this:
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ %{SERVER_PROTOCOL}://www.%{HTTP_HOST}/$1 [R,QSA]
-- =
Rik Wasmus
Posted on Usenet: any site claiming this as original content or me as an=
=
contributing member is stealing content.
Ask Smart Questions: http://tinyurl.com/anel
Navigation:
[Reply to this message]
|