WebPagetest Forums
Fastest . => www. Redirect? - Printable Version

+- WebPagetest Forums (https://www.webpagetest.org/forums)
+-- Forum: WebPagetest (/forumdisplay.php?fid=7)
+--- Forum: General Discussion (/forumdisplay.php?fid=25)
+--- Thread: Fastest . => www. Redirect? (/showthread.php?tid=13757)

Fastest . => www. Redirect? - MarkForst - 06-05-2015 07:41 AM

Hi folks,

how is it possible to get instant redirects like from

nytimes.com => http://www.nytimes.com

its crazy fast. can anyone tell me how big sites are able to do that? when i hit enter i instantly ge the => www. redirect..

thanks a lot for your help!

RE: Fastest . => www. Redirect? - WebsiteSpeedExperts - 06-06-2015 09:04 AM

Most websites use a htaccess or http config redirect which will redirect the visitor prior to the server hitting something like the php hypervisor. What thia means in general terms is that the site admins configure their server to send and traffic which matches certain patterns to another address and thwn close the connnection.

RE: Fastest . => www. Redirect? - Fleck_Lannis - 06-07-2015 10:16 PM

I think thats not really the point. Of course you need use htaccess instead of i.e. some wordpress or php 301.

but still, if you use htaccess on a "normal" website, you will never get these extreme fast redirects to www as for example on http://nytimes.com

I would also be very interested how this is possible. any ideas?

RE: Fastest . => www. Redirect? - josephscott - 06-10-2015 04:43 AM

A request to nytimes.com responds with "HTTP/1.1 301 http://www.nytimes.com/", so nothing particularly special going on there.

They are using Varnish, so it could be that is where they've configured the redirect.

RE: Fastest . => www. Redirect? - JamesAtPulsate - 06-10-2015 07:13 AM

43ms is nice alright. Of course it's not being directed to https so that helps some. I wonder if varnish plays a role in that 43ms time.


RE: Fastest . => www. Redirect? - pmeenan - 06-10-2015 11:33 PM

As far as your local experience goes, a 301 is a cacheable "permanent" redirect to the browser remembers it and never sends the original request.