[Webkit-unassigned] [Bug 249766] Push to expired endpoint returns 200 still

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=249766

Ben Nham <nham at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |nham at apple.com
         Resolution|---                         |WONTFIX

--- Comment #2 from Ben Nham <nham at apple.com> ---
Thanks for your bug report. We reached out to the server team about this. There are a couple of things to consider here:

1. We do not guarantee that unsubscribing from Web Push will always result in a state where sending a push to the associated endpoint returns a 410 Gone. There are various error states which can cause the unsubscribe event to not be sent or processed successfully by the push server.

2. Even when the unsubscribe event is processed successfully by the push server, there is a non-deterministic delay between when the unsubscribe event is processed and when sending a push to the associated endpoint returns a 410 Gone. This delay is in place for privacy reasons.

If you want to ensure that you only track one push subscription per user session, you can send the current push subscription associated with the session to your backend when the user visits your website (e.g. by XHRing the result of PushManager.getSubscription to your backend). You can then use the current subscription data to prune any non-matching subscriptions.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230104/1ab1964a/attachment.htm>