1222428 - cleaning dom.push.userAgentId does not expire the subscription in push server

Status: RESOLVED FIXED

(Cloud Services Graveyard :: Server: WebPush, defect)

Description

[Piotr Zalewa [:zalun]]

Server is still responding with 200 to push notification request after dom.push.userAgentId is set to "". pushsubscriptionchange is fired.

Comment 1

[Lina Butler (ex-Mozilla)]

Unfortunately, this is working as intended: there's no way for Firefox to tell the server that the old ID is no longer valid; only the other way around. (The old subscriptions will be garbage-collected eventually, but I think that kicks in after about a month).

I wonder if it's worthwhile adding this to the protocol, though. If a user resets the `dom.push.userAgentID` pref, the server will still accept (and store!) messages for old subscriptions, for a device that will never get them. At the very least, we should restrict the number of outstanding messages that we store on the server. I know we talked about this, but I don't know if we do it already.

Flagging Ben for comment.

Comment 2

[Lina Butler (ex-Mozilla)]

Michelle, I think you asked about this bug in this morning's meeting. Android doesn't use `dom.push.userAgentID` (it uses Google Cloud Messaging, which issues its own IDs). It's expected that the value of this pref will be empty.

Comment 3

[Michelle Funches - QA]

Acknowledge: thanks for explaining. We will test for Desktop only.

Comment 4

[Ben Bangert [:benbangert]]

We have a ticket that will cause a reset of the userAgentID if 'too_many_messages_are_stored'. This will prevent excessive notifications from piling up, and start returning 410's to the push notification request.

Comment 5

[JR Conlin [:jrconlin,:jconlin]]

I believe that this has been resolved. Closing