- From: Noam Rosenthal <notifications@github.com>
- Date: Tue, 04 Jul 2023 04:09:13 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/1647/c1620044733@github.com>
> Thank you noamr@! I've added some last comments. And also added the missing features from the original proposal belows. Please let us know if they are suitable here. > > 1. It is suggested to allow only secure requests for new API in [Do we want to enforce HTTPS request? WICG/pending-beacon#27](https://github.com/WICG/pending-beacon/issues/27). Should we enforce HTTPS-only requests on `fetchLater()`? Probably a good idea, from the point of view of enabling new features only for secure requests. > 2. Should this spec mention [Permission Policy]https://www.w3.org/TR/permissions-policy/? In [[Fetch-Based API] Permissions Policy WICG/pending-beacon#77](https://github.com/WICG/pending-beacon/issues/77), the suggestion is to allow the API by default. But we might want to provide a way to manage 3rd party iframe's usage. I don't think we should integrate with permission policy. But we should allow the user agent to deny a `fetchLater` and throw an error immediately. I'll add that to the PR. > 3. [Consider to support retry mechanism WICG/pending-beacon#40](https://github.com/WICG/pending-beacon/issues/40) Should this spec mention retry when `fetchLater()` fails to send/commit? Perhaps consider adding this later? > 4. The original PendingBeacon proposal also includes [Crash recovery WICG/pending-beacon#34](https://github.com/WICG/pending-beacon/issues/34), not sure how it can be incorporated into fetch spec. I don't think that changes anything in the spec. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1647#issuecomment-1620044733 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1647/c1620044733@github.com>
Received on Tuesday, 4 July 2023 11:09:18 UTC