- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 10 Mar 2021 07:16:52 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 10 March 2021 15:17:04 UTC
In the case where they don't match it becomes a network error in HTTP/1 (maybe also other versions, unclear). https://fetch.spec.whatwg.org/#content-length-header is the start toward documenting that. However, we are not using `Content-Length` to parse the response as we do when a response comes from the network. E.g., a `Content-Length` on a synthetic response that's too long or too short doesn't influence the body of the response one way or another. So I don't think looking for precedent there is meaningful. -- 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/ServiceWorker/issues/1571#issuecomment-795587611
Received on Wednesday, 10 March 2021 15:17:04 UTC