Re: [fetch] Access to the HTTP trailer (#34)

We can't have a cache carveout for trailers if we expose them. That we drop them on the floor is precisely the reason it's okay that we don't put them in the cache. As soon as that changes, this no longer holds.

Imagine a resource which sends `max-age=99999999` and sends a trailer. So you `fetch()` it, you read out the trailers. Random JS code does whatever it wants with said trailer. Hooray.

Now we `fetch()` it again. The cache entry is used without revalidation. We didn't save the trailers, so they don't get sent up this down. And now the JS code is confused because the trailers suddenly disappeared.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/34#issuecomment-123087186