Push API not respecting time-to-live
Reported by
jack.ler...@braze.com,
May 22 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1. Send push message with 60 second time-to-live in headers 2. Wait 70 seconds 3. Open Browser and push is still delivered What is the expected behavior? After 60 seconds, push service should discard the message and not deliver it to the browser. What went wrong? Chromium is not interpreting the time to live value correctly and so waiting for the device to come back online and then still delivering the push Did this work before? N/A Does this work in other browsers? Yes Chrome version: 65.0.3325.181 Channel: stable OS Version: Windows 10 Flash Version: 29.0.0.171
,
May 22 2018
,
May 22 2018
Jack: Can you provide some code snippets to clarify the components in question?
,
May 22 2018
If you can reliably reproduce this, could you make a screenshot of chrome://gcm-internals showing the received notification? The server logs should be able to tell us more about what's going on.
,
May 23 2018
Hi all, Problem is actually being experienced by a customer. I will follow up with them and ask them to reproduce and provide screenshots and code snippets if possible. Thanks!
,
May 23 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 23 2018
,
Jun 22 2018
No feedback was received in the last 30 days from the reporter, so archiving this issue. Please re-open or file a new bug if necessary. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by sindhu.chelamcherla@chromium.org
, May 22 2018