Re: [whatwg/fetch] Cloned responses should not have immutable headers (#608)

> I suspect your concern is with inputs where the guard is "immutable" and therefore the clone being "immutable" too.

Yep, that's exactly my concern. And more specifically *should* this be the case for cloned response objects?

It's also entirely possible that my use case (adding metadata to a `Response`) could be handled in some different way, which I'm open to.

Effectively, what I'm after is a reasonable way to communicate back to the window whether this particular response came from the cache or from the network.


-- 
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/608#issuecomment-332672468