- From: Jake Archibald <notifications@github.com>
- Date: Sat, 14 Apr 2018 18:08:45 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 15 April 2018 01:09:10 UTC
@csreis > Just to clarify, are you saying that multipart range requests wouldn't generate responses with multipart/byteranges content types after your changes? I'm saying that the browser shouldn't ever ask for multiple ranges in a single request. Is there anywhere we do this today? Or am I misunderstanding what you mean by multipart request? > To be clear, I think we're ok with having blocked responses end up in the cache in general I think it's easiest if the body is replaced with an empty body long before it ends up in the cache API. I'm happy with these empty-body responses ending up in the cache. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/681#issuecomment-381372587
Received on Sunday, 15 April 2018 01:09:10 UTC