- From: Lars G. Svensson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jun 2018 07:39:20 +0000
- To: public-dxwg-wg@w3.org
@jakubklimek scripsit: >Another way of doing this is saying that we leave compression to HTTP server and client (restriction to HTTP), the server can use gzip_static to serve the .trig.gz file from its file system and the client decompresses it transparently in the HTTP layer. This means the Distribution still points to the .trig file, the media type is application/trig, and it is completely opaque to the user. And a third way is to configure the web server to look at both `Accept` and `Accept-Encoding`. If we for instance have * https://example.org/datasets/ds1.jsonld.gz * https://example.org/datasets/ds1.xml.gz and an agent sends ``` GET /datasets/ds1 Accept: application/ld+json Accept-Encoding: gzip ``` the server would return https://example.org/datasets/ds1.jsonld.gz whereas a request for ``` GET /datasets/ds1 Accept: application/xml Accept-Encoding: gzip ``` would return https://example.org/datasets/ds1.xml.gz Cf. [RFC 7231 ยง5.3.4](https://tools.ietf.org/html/rfc7231#section-5.3.4) -- GitHub Notification of comment by larsgsvensson Please view or discuss this issue at https://github.com/w3c/dxwg/issues/259#issuecomment-400573957 using your GitHub account
Received on Wednesday, 27 June 2018 07:39:24 UTC