From: "Ludovic Courtès" <ludo@gnu.org>
To: Peng Mei Yu <pengmeiyu@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Let guix client accept HTTP redirection
Date: Mon, 14 Dec 2020 11:00:12 +0100 [thread overview]
Message-ID: <87im94vhar.fsf@gnu.org> (raw)
In-Reply-To: <87tusuidyk.fsf@riseup.net> (Peng Mei Yu's message of "Thu, 10 Dec 2020 10:37:07 +0800")
Hi,
Peng Mei Yu <pengmeiyu@riseup.net> skribis:
> Good news. The maintainers of mirrors.sjtug.sjtu.edu.cn (an academic
> free software mirror site) agreed to accept Guix into their support
> list.
Nice!
> Bad news. Their first implementation of a Guix mirror failed. Their
> server architecture is like this: A front-end program accepts HTTP
> requests. It looks up the requested resource from a storage server
> similar to Amazon S3. If the resource is found on storage server,
> return an HTTP 302 redirection to the storage server. If the resource
> is not found, return an HTTP 302 redirection to ci.guix.gnu.org and
> fetch the resource from ci.guix.gnu.org then store it in the storage
> server. So the next time the same resource is requested, it can be
> served from the storage server.
>
> During the test, we found that guix client does not accept HTTP 302
> redirection. So we are working on a different implementation. In the
> meantime, I think the problem should be reported here and let's find out
> if something can be done from the Guix side.
Yes, people reported that issue just recently:
https://issues.guix.gnu.org/45174
Until that is fixed, and until the fix propagates to user installations,
I think you’ll have to arrange so that the mirror transparently proxies
requests instead of returning 302, or just returns 404. How does that
sound?
Thanks,
Ludo’.
prev parent reply other threads:[~2020-12-14 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 2:37 Let guix client accept HTTP redirection Peng Mei Yu
2020-12-14 10:00 ` Ludovic Courtès [this message]
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=87im94vhar.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=pengmeiyu@riseup.net \
/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).