Support gzip/brotli compressed assets about qvis HOT 3 OPEN

treat .qlog.zip, .qlog.gz and .qlog.br as normal .qlog in both qvis and qvis-server

Don’t you have to gunzip it first?

from qvis.

I'm hoping that I can download them at the server and then just set the correct content_encoding when sending it back to the frontend, allowing the browser to do the decompression... hoping being the keyword there ;)

from qvis.

Update:
1: This cannot be done directly in the browser. So now we just look for an error. If we get that, we try again via the server (if it was a genuine 4xx the first time we wasted another request, but too bad)

2 - 4: 29d3aaa, bab59db and quiclog/qvis-server@3759662. Our hope was valid: qvis-server can just proxy the files and set the correct Content-Encoding and it works (or at least it seems to ;))

As a side-effect, we now also try to fetch files inside the browser first. If CORS is setup properly, no more backend interaction is necessary!

5: TODO

Some testfiles one can use:

• https://qlog.edm.uhasselt.be/anrw/files/compressed/test_minified.qlog: implicitly gzip compressed (see Content-Encoding header). CORS-enabled, so fetched directly from browser.
• https://qlog.edm.uhasselt.be/anrw/files/compressed/test_minified.qlog.gz: explicitly gzip compressed. CORS-enabled, so fetched directly from browser.
• https://qlog.edm.uhasselt.be/anrw/files/compressed/test_minified.qlog.br: explicitly brotli compressed. CORS-enabled, so fetched directly from browser.
• https://qlog.edm.uhasselt.be/anrw/files/compressed/test_minified.qlog.br.nocors: explicitly brotli compressed. Not CORS-enabled, so fetched from backend server as fallback.

from qvis.