Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Clearing brower cache history and web push endpoint's expiration

  • 1 wótegrono
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót Arturo01

more options

A user has an endpoint and receives web push. But if he clears his browser cache, he won't receive web notifications anymore.

So this endpoint becomes kind of "expired". However, if we try sending a push to this user, Mozilla always returned a "201 Created".

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 ?

Thanks

A user has an endpoint and receives web push. But if he clears his browser cache, he won't receive web notifications anymore. So this endpoint becomes kind of "expired". However, if we try sending a push to this user, Mozilla always returned a "201 Created". 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 ? Thanks

Wšykne wótegrona (1)

more options

Mozilla has been working on this unwanted behavior : https://bugzilla.mozilla.org/show_bug.cgi?id=1277615

It is now fixed with Firefox Developer Edition v49 and it returns a errno106 - No such subscription in this situation.