Re: Mandating a default client timeout for HTTP 301

On 1 Dec. 2017 03:54, "Barry Tunetheweb" <barry@tunetheweb.com> wrote:

First time poster, long time lurker, so be nice if I’m wrong about this :-)

The semantics of the status code -- for better or worse -- aren't tied to
> caching, so this would be a pretty big change. We're generally shy of doing
> that unless there's a significant interoperability or security issue, and
> this sounds like it's more of a developer usability issue -- i.e., people
> should have used a temporary, rather than a permanent redirect.
>

I would argue that it IS tied to caching - by most browsers making it
permanently cached as well.



I wasn't aware that browsers cache the 301. (I mean, maybe if you send the
right combination of cache headers along with the response...) And even if
they do, doesn't "forever" in a browser cache usually mean a couple of
months (assuming no further hits)?

I always read 301 as about updating bookmarks, crawler/search indices, etc.

Cheers
-- 
Matthew Kerwin