Live data from Hacker News

Tangled issues with permanent HTTP redirects

utcc.utoronto.ca

11–15 of 15 posts

Re: Tangled issues with permanent HTTP redirects

#11
post #8

There seems to be some FUD going on here. The solution to the OP problem is simply to use 301 redirects with Cache-Control headers to limit caching to some reasonably short duration. It is true that browsers will cache 301 redirects eternally, but only if the server does not supply cache directives to indicate otherwise. For this reason, it is always advisable to include some cache directives in 301 redirect response…

Thank you for taking the time to post such an insightful message.

Re: Tangled issues with permanent HTTP redirects

#12
post #6

If it's not permanent then just keep it temporary... I don't see the problem here

Part of the problem is the belief that a 301 is the best option for SEO because it passes 'link juice'. Evidence for this being true will always be some random blog post from a self proclaimed expert. My default option is always a 302 for the simple fact that it isn't going to be cached and can be easily changed with no ill effects. I've yet to notice any disadvantage from an seo point of view.

What is "link juice here?

Re: Tangled issues with permanent HTTP redirects

#13
post #6

Earlier quoted context omitted.

Part of the problem is the belief that a 301 is the best option for SEO because it passes 'link juice'. Evidence for this being true will always be some random blog post from a self proclaimed expert. My default option is always a 302 for the simple fact that it isn't going to be cached and can be easily changed with no ill effects. I've yet to notice any disadvantage from an seo point of view.

What is "link juice here?

Link juice is the term used in the SEO world to refer to the value or equity passed from one page or site to another. This value is passed through hyperlinks. Search engines see links as votes by other websites that your page is valuable and worth promoting.

https://www.woorank.com/en/edu/seo-guides/link-juice

Re: Tangled issues with permanent HTTP redirects

#14
post #8

There seems to be some FUD going on here. The solution to the OP problem is simply to use 301 redirects with Cache-Control headers to limit caching to some reasonably short duration. It is true that browsers will cache 301 redirects eternally, but only if the server does not supply cache directives to indicate otherwise. For this reason, it is always advisable to include some cache directives in 301 redirect response…

In this case, permanent == indefinite, and temporary == ephemeral is a good way to think of it.

Re: Tangled issues with permanent HTTP redirects

#15
post #14
post #8

There seems to be some FUD going on here. The solution to the OP problem is simply to use 301 redirects with Cache-Control headers to limit caching to some reasonably short duration. It is true that browsers will cache 301 redirects eternally, but only if the server does not supply cache directives to indicate otherwise. For this reason, it is always advisable to include some cache directives in 301 redirect response…

In this case, permanent == indefinite, and temporary == ephemeral is a good way to think of it.

Those are good words to use. That's how people should think of these redirects and use them, as long as you are careful to use explicit cache directives.
Post reply on HN