Closed Bug 1277615 Opened 9 years ago Closed 9 years ago

Clearing brower cache history and web push endpoint expiration problem

Categories

(Core :: DOM: Push Subscriptions, defect)

46 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1275436

People

(Reporter: alting, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160511224433 Steps to reproduce: User-side: - generating an endpoint with a `serviceWorkerRegistration.pushManager.subscribe()` - sending web notifications to the endpoint (push is well sent and received) - clearing cache browser history - again, sending a web notification (push is not received, a new endpoint need to be generated) => So, a user has an endpoint and receives web push. But if he clears his browser cache, he won't receive web notifications anymore. This endpoint becomes kind of expired". Actual results: Server-side: If we send a push to the "expired" endpoint (as described above), Mozilla always returned a "201 Created" Expected results: Server-side: In this specific case, could you return an error, e.g. "errno 103 - Expired URL endpoint", telling us that this endpoint won't receive web notifications anymore ?
Reproducible Version 49.0a1 Build ID 20160606030219 User Agent Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Status: UNCONFIRMED → NEW
Component: Untriaged → Notifications and Alerts
Ever confirmed: true
Product: Firefox → Toolkit
Thanks! This should be fixed by bug 1275436, which will be available in tomorrow's Nightly. If you clear "Site Preferences" in History > Clear Recent History, or use the "Forget" button, it'll remove the subscriptions from the server.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Component: Notifications and Alerts → DOM: Push Notifications
Product: Toolkit → Core
You need to log in before you can comment on or make changes to this bug.