Re: [w3c/push-api] The user agent should be permitted to acknowledge even if the SW rejects (#196)

Elio Damaggio made a related proposal in the WebPush WG to allow user agents to return opaque diagnostic data to their application servers in an optional Acknowledgement-Data header forwarded by the push service with an acknowledgement.  We closed the issue until we had more clarity if there was demand for such a feature. 

Something along the lines of:

_If a push message has a Push-Receipt header field, the user agent MAY include exactly one “Acknowledgement-Data” header field in its acknowledgement request.  The content of the Acknowledgement-Data header field is opaque diagnostic data  encoded as a base64url string. The ABNF [RFC5234] production for "token68" is defined in Section 2.1 of [RFC7235]._

_If the application has requested a delivery receipt, the push server MUST include the Acknowledgement-Data header field with the response to the application server monitoring the receipt subscription resource._  


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/196#issuecomment-225006215