Re: [whatwg/fetch] Option to fetch raw byte as is. (without decompressing) (Issue #1524)

Here is a compelling case for a Chrome extension:

1. We have a Chrome extension that emulates other browsers using a remote host to do the rendering.
2. Because the rendering host might not have access to the local client's VPN, we allow an option wherein the extension in the local client implements a tunnel so the HTTP requests from the rendering host can be sent back through the client, thus able to retrieve resources from within the VPN.
3. We need to be able to then send the uncompressed responses back to the rendering host.
4. We have done this successfully with XMLHttpRequest and this works for many scenarios, but now service workers are required, thus Fetch is required.
5. The alternatives are not good, like re-compressing those responses using a gzip compression library.  Or mucking with the headers to send a decompressed response, but this was causing other issues that we did not pursue, because it is clearly not desirable.  Or, send the request over to a tab page (which we would have to open if there isn't one), have the tab page make the request using good old XHR, then send the response back to the service worker, then back to the rendering host.  Again, yuck.
 




-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1524#issuecomment-1335874318
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1524/1335874318@github.com>