up vote 0 down vote favorite

I want to redirect mysite.com or http://mysite.com or www.mysite.com or any other format given my user to http://www.mysite.com, I'm able to achieve this by rewriting following lines in my .htaccess file

Rewritecond %{http_host} ^mysite.com
RewriteRule ^(.*) http://www.mysite.com/$1 [R=301,L]

But I want do this from Apache,So I've added following line in Virtual host conf file of the site and removed above two lines from .htaccess

Redirect 301 / http://mysite.com/

But whenever I'm trying to access the site following error is displyaing,

Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.

where I'm doing the wrong ?

share|improve this question
isn't this a predestined question for serverfault? – DKOATED 2 days ago
I thought this question might suitable here, if not please flag it – Mahesh.D 2 days ago
1  
i flagged, but to be of help, the 310 error indicates that you have a redirection loop going on. i also suspect that the "Redirect 301" is wrong, seems to me you are redirecting from the root directory to mysite.com (which is also the root directory)... hence you get an infinite loop. – DKOATED 2 days ago
@DKOATED: Thanks – Mahesh.D 2 days ago
@DKOATED: Thanks, after removing the / then its working as expected. – Mahesh.D 2 days ago
show 3 more comments

2 Answers

up vote 0 down vote

Your directive causes an infinite redirection loop.

The reason is that a 301 gets returned to the browser and that host and path are really separate things, despite forming a URL. When a browser sees a 301 redirect to http://site.com/ it interprets it as find site.com and ask for the / path from the standard HTTP port.

With your unconditional rule, which is valid for site.com, the 301 is returned again which sends them in an infinite loop.

share|improve this answer
up vote 0 down vote

What you want is this:

RewriteCond %{HTTP_HOST}   !^www\.example\.com [NC]
RewriteCond %{HTTP_HOST}   !^$
RewriteRule ^/(.*)         http://www.example.com/$1 [L,R]

which was copied directly from here. You really ought to read through that page and understand it.

Your current rewrite rule, as it stands, sends every request to a local server path that your apache config probably cannot deliver ('/' is the root directory of your server not the root of your website). Apache in turn will try to respond to that with an error page, which in turn gets redirected to the '/' again, hence an infinite redirect.

The above code only redirects requests NOT bound for www.example.com and preserves the rest of the URL when it redirects.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.