From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: [maintenance] Compressed JSON files and served file extension?
Date: Thu, 16 Nov 2023 15:40:34 +0100 [thread overview]
Message-ID: <87jzqhwyl9.fsf@gnu.org> (raw)
In-Reply-To: <861qe03rtj.fsf@gmail.com> (Simon Tournier's message of "Thu, 12 Oct 2023 15:15:20 +0200")
Simon Tournier <zimon.toutoune@gmail.com> skribis:
> However, now I get:
>
> $ wget https://guix.gnu.org/sources.json
If you open it in a browser though, it’s fine, because browsers and in
fact many HTTP clients other than wget, honor ‘Content-Encoding’:
--8<---------------cut here---------------start------------->8---
$ wget -O/dev/null --debug https://guix.gnu.org/sources.json
[...]
---response begin---
HTTP/1.1 200 OK
Server: nginx
Date: Thu, 16 Nov 2023 14:38:04 GMT
Content-Type: application/json
Content-Length: 2670848
Connection: keep-alive
Content-Encoding: gzip
Expires: Thu, 16 Nov 2023 17:38:04 GMT
Cache-Control: max-age=10800
Content-Security-Policy: frame-ancestors 'none'
--8<---------------cut here---------------end--------------->8---
[...]
> Well, it will break some consumers of packages.json and sources.json.
> To my knowledge, for sources.json at least, the only consumer is SWH and
> it appears to me easy to keep them in touch. :-)
It shouldn’t break consumers, their client will just transparently
decompress the stream (I checked with #swh-devel back then just in
case).
That said, if you become aware of actual breakage, we can revisit this!
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-11-16 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 13:15 [maintenance] Compressed JSON files and served file extension? Simon Tournier
2023-11-16 14:40 ` Ludovic Courtès [this message]
2023-11-20 9:49 ` Simon Tournier
2023-11-28 13:48 ` Simon Tournier
2023-11-28 15:57 ` Tomas Volf
2023-11-20 14:03 ` Attila Lendvai
2023-11-28 13:37 ` Simon Tournier
2023-11-28 15:50 ` Tomas Volf
2023-11-28 21:05 ` Attila Lendvai
2023-11-29 9:08 ` Simon Tournier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzqhwyl9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).