Re: [Webpush] Message expiration (TTL) and Negative Acknowledgements

I'm not sure if this relates, but there are a few implementation status
codes that might be useful. We've seen the following sorts of situations
arise and it would be good to have developers aware of them.

301 & 307: The resource has either moved permanently or temporarily.
(This may occur if a service in maintenance or if a service was shut
down and traffic needs to be reallocated.)  In the case of a 301
response, all future traffic should be permanently routed to the new host.

429: This will allow the server to apply "back pressure" to the
application service in cases where there may be too many incoming
messages in a short period of time. This response would carry a
RETRY-AFTER response header indicating the number of seconds that should
elapse before the remote server should retry transmission of the message.

On 10/13/2015 4:10 PM, Martin Thomson wrote:
> On 13 October 2015 at 15:32, Brian Raymor <Brian.Raymor@microsoft.com> wrote:
>> Then, we're in agreement. When a receipt is requested, the same 5xx status code is returned for either giving up prior to the original expiration or lowering the advertised message expiration and failing to deliver.
> WFM.  Now, if only we could decide on what that 5xx might be (or was
> your intent to follow-up with a mail on that subject.)
>
> _______________________________________________
> Webpush mailing list
> Webpush@ietf.org
> https://www.ietf.org/mailman/listinfo/webpush