Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 errors increased dramatically after 20 June 2024 #405

Open
ozgurhangisi opened this issue Jul 4, 2024 · 4 comments
Open

404 errors increased dramatically after 20 June 2024 #405

ozgurhangisi opened this issue Jul 4, 2024 · 4 comments

Comments

@ozgurhangisi
Copy link

Hello,

We are a push provider company and we have lots of clients. Our old clients has so many (almost %40-50 of total subscribers ) 404 errors after 20 june 2024. We don't use firebase api, we directly send webpushes via VAPID. Does anyone experienced similar problem? We have no problem with new clients.

@Minishlink
Copy link
Member

Hello, are these endpoints like https://fcm.googleapis.com/fcm/send ? Cf. https://firebase.google.com/support/faq?hl=fr#fcm-23-deprecation I would assume they didn't come back to the website and you didn't receive the new google endpoint?

@ozgurhangisi
Copy link
Author

Hello, yes all of the chrome endpoints starts with https://fcm.googleapis.com/fcm/send.

But new endpoints also starts with https://fcm.googleapis.com/fcm/send. So Does that mean that all of our clients endpoints will be expired?

@Minishlink
Copy link
Member

It doesn't look like it https://stackoverflow.com/questions/77957644/will-fcm-ditch-the-support-of-web-push-protocol
Maybe the 404s were a temporary regression on their side?

@ozgurhangisi
Copy link
Author

https://pushpad.xyz/blog/fcm-returns-404-for-stale-push-subscriptions

This article explains why there are lots of expired endpoints. Google started to remove endpoints that doesn't have any signal in 90 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants