W3C home > Mailing lists > Public > www-qa@w3.org > March 2004

RE: Don't use "refresh" to redirect

From: Brian Kelly <B.Kelly@ukoln.ac.uk>
Date: Thu, 4 Mar 2004 14:30:53 -0000
To: 'Jens Meiert' <jens.meiert@erde3.com>
Cc: jc@jcrompton.de, www-qa@w3.org
Message-ID: <10403041433.aa24255@lamin.ukoln.ac.uk>


> > Is a server-side redirect totally wihout problems?
> 
> It's not inevitably unproblematic, but there are at least three major
> advantages:
> 
> - It works (for example, JavaScript could be disabled).
> - You can specify the type of the redirect (in .htaccess), 
> e.g., a 301 represents a permanently moved resource, while 
> 307 indicates a temporarily shifted file.
> - (Impaired) users normally don't notice a server-side 
> redirect, but using a meta redirect (especially when also 
> using a delay) might be quite irritating.

Yes I agree with all of this.  I wasn't arguing for client-side redirects, I
was seeking to clarify possible side-effects of server-side redirects.

Perhaps we need a "Use server-side redirects correctly" tip.

Brian
 
> Best regards,
>  Jens.
> 
> 
> --
> Jens Meiert
> Interface Architect
> 
> http://meiert.com/
> 
> 
Received on Thursday, 4 March 2004 09:33:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 12:14:00 GMT