Closed KonradHoeffner closed 1 month ago
We are looking into this ...
This has been fixed by commit https://github.com/openlink/virtuoso-opensource/commit/a09ba100dec26a428a642325856da848eacc847f on the develop/7 branch.
I pushed a new docker image pkleef/virtuoso-opensource-7:latest
to Dockerhub.
Can confirm, this works perfectly with:
docker run --rm --network=host -e VIRT_HTTPSERVER_ENABLEDGZIPCONTENT=1 pkleef/virtuoso-opensource-7
According to the docs, (see quote below),
EnabledGzipContent
invirtuoso.ini
orhttp_enable_gz(1);
in ISQL should enable HTTP compression:However both of these don't work:
According to the DockerHub documentation,
virtuoso.ini
variables can be set via environment variables asVIRT_SECTION_KEY=VALUE
. Following this scheme, we should activate it using `VIRT_HTTPSERVER_ENABLEDGZIPCONTENT=1´. However when we run virtuoso as a docker image as follows, we don't get compressed results:If we open
http://localhost:8890/sparql
, the Firefox and Chrome web developer tools in the network tab do not show any compression, although gzip is requested:Request Headers
Response Headers
For comparison, when opening https://dbpedia.org/sparql, I get this:
Note the
Content-Encoding: gzip
.Also discussed in https://stackoverflow.com/questions/78819781/how-to-compress-query-results.