Re: [w3c/push-api] Add a way to cancel previous push notification (Issue #399)

martinthomson left a comment (w3c/push-api#399)

The original idea for this was to allow a DELETE on the resource that was created by the push service when a message is posted.

See https://datatracker.ietf.org/doc/html/rfc8030#section-5.4 for an example of replacement.  In addition to that, you might imagine that a push service could support deletion.

From a request:

```http
POST /push/JzLQ3raZJfFBR0aqvOMsLrt54w4rJUsV HTTP/1.1
Host: push.example.net
TTL: 600
Topic: upd

... message contents ...
```

To which the server responds:

```http
HTTP/1.1 201 Created
Date: Thu, 11 Dec 2014 23:57:02 GMT
Location: https://push.example.net/message/qDIYHNcfAIPP_5ITvURr-d6BGt
```

That example shows the message contents being replaced, but they could also be replaced with nothing (i.e., removed) as follows:

```http
DELETE /message/qDIYHNcfAIPP_5ITvURr-d6BGt
Host: push.example.net
```

Using the "Topic" field to enable this ensures that the push service is able to know which messages to enable this treatment for, but it's equally possible that this could be done for all messages.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/399#issuecomment-2764887594
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/399/2764887594@github.com>