Re: UA norm for redirects (both META and http)

Justin James wrote:
> The issues that the original request attempts to address, in terms of how browsers handle the redirect. Basically, my suspicion is that application developers don't realize that multiple HTTP status codes can produce a redirect, and they may have a redirect reason or two that the existing status codes don't cover. What I see is that developers tend to use 302 (Moved) which is rarely the correct status code for what they are trying to accomplish. So between developers frequently operating in a state of ignorance, and the HTTP spec not fully meeting their needs (although experience shows that few would use the needed feature if they were added anyways), we have a scenario where the browser's behavior is often not ideal.

That may all be true, but I'm not sure how this is HTTP's problem.

HTTP basically distinguishes "moved temporarily" and "moved 
permanently". Are you looking for more detail? What? And what would a UA 
do with it?

BR, Julian