Re: Redirects in g2_import; 302 (current behavior) vs 301 (proposed)

Huh, that's an oversight.  We should be using 301s not 302s because for
most users this will not be a temporary transition.


On Thu, Jan 31, 2013 at 2:59 AM, Mike Miller <[email protected]> wrote:

> Rather than submit a pull request, I wanted to ask first:
>
> Do you think that the correct API to use in g2_import is
> url::redirect(), which returns a 302 (temporary redirect)? I always
> assumed that the normal case of migration is non-reversible; should we
> send a 301 instead (which, among other things, will tell most search
> engines to stop hitting the old URL)?
>
> Alternatively, do you think this should this be abstracted into an
> option so the user can select 301 or 302?
>
> -- Mike
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_jan
> __[ g a l l e r y - d e v e l ]_________________________
>
> [ list info/archive --> http://gallery.sf.net/lists.php ]
> [ gallery info/FAQ/download --> http://gallery.sf.net ]
>
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan

__[ g a l l e r y - d e v e l ]_________________________

[ list info/archive --> http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download --> http://gallery.sf.net ]