Closed drott closed 6 years ago
I'm guessing this is more a Vapid error than a pywebpush error.
Clock skew is always a problem, and the obvious work-around is to specify an exp
yourself.
I'll consider reducing the default period to 12 hours, and file the bug on the py-vapid library.
Thanks, yes, let's move it to: https://github.com/web-push-libs/vapid/issues/56
In my experience, the default expiry of 24hours might be causing errors on the push backends of Google and Mozilla. They reject the request, with Mozilla reporting that the expiry is too far in the future, probably due to slight clock differences.
I would suggest to reduce the default expiry time in order to avoid such problems.