Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Changing back the default redirect code from 301 to 302. #1619

Merged
merged 1 commit into from
Aug 23, 2017
Merged

Changing back the default redirect code from 301 to 302. #1619

merged 1 commit into from
Aug 23, 2017

Commits on Aug 23, 2017

  1. Changing back the default redirect code from 301 to 302. 

    A permanent redirect can not be changed remotely once it has been sent.

Permanent redirects (301 / 308) are exactly what the their descriptive
name suggest. A 301 or 308 will be indefinitely cached client-side,
sometimes even when a user clears their cache.

They should be used to keep search engine page rankings by sending a
permanent redirect on a page by page basis, not for site to site or
protocols (http to https).

Especially on a new Grav installation, the default should not be 301.

My reasoning is that with the first visit to a new installation, before
even doing anything else, the 301 is already permanently cached in the
browser.

Additionally, temporary redirects can be influenced remotely and are not
that expensive on the webserver nowadays with event-based handlers.
    Daniël Mostertman committed Aug 23, 2017
    Configuration menu
    Copy the full SHA
    da72fb6 View commit details
    Browse the repository at this point in the history