Re: Possible need for new 3xx status code Temporarily See Other

Hello,

On Wed, Sep 25, 2024 at 11:37:37PM +0000, Belov, Charles wrote:
> This is a comment on HTTP/1.1, part 2: Message Semantics
> draft-ietf-httpbis-p2-semantics-16
> 
> We have a situation where, to prevent server overload, we temporarily can't
> serve the desired resource but can serve a related resource that may be
> helpful. We don't want search engines to register this as an update to our
> website.
> 
> We have settled on 307 Temporary Redirect. But that's not accurate, because
> it's not a temporarily moved resource, it's a substitute resource. So 303 See
> Other would in theory be more appropriate.
> 
> But 303 See Other might be taken as stating that the requestor should ask for
> this other resource in the future, which might cause search engines to update
> their index, which we don't want to happen.
> 
> It would be nice to have a 3xx status code for Temporarily See Other to get
> across that we are only serving this other resource temporarily and that
> future requests should be for the original request.

Just an idea, but wouldn't an Expires response header field suffice to
limit the validity period of the 303 ?

Regards,
Willy

Received on Thursday, 26 September 2024 03:42:08 UTC