From: Christopher Meng <i@cicku.me>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin@cygwin.com
Subject: Re: Mirror announcement
Date: Tue, 26 Mar 2024 14:13:18 -0400 [thread overview]
Message-ID: <7475E6CC-779B-499D-AD51-A50FE2AA98CE@cicku.me> (raw)
In-Reply-To: <f09fe102-b79f-4d54-87e0-77bea162065c@dronecode.org.uk>
Hi,
UA could be something unique similar to “Cygwin mirror/0.01” and I can whitelist then, but having “python-urlli will definitely trigger the WAF.
While I can completely disable the check without issues, if you want to carry a specific UA feel free to do it and I will then white list based on UA.
Let me know when you are ready.
Sent from my iPhone
> On Mar 26, 2024, at 1:40 PM, Jon Turney <jon.turney@dronecode.org.uk> wrote:
>
> On 26/03/2024 14:10, Christopher Meng via Cygwin wrote:
>> Hi, This mirror is actually behind CDN which is "global", so I'm not sure if you can handle such of mirror on your end for redirect.
>
> OK, I'll leave the location unspecified.
>
> I gave it a brief test with our setup program and things seem to work correctly (which shouldn't be surprising since it just uses the wininet
> API to fetch files).
>
> However, it seem our mirror checking script seems to get told "403 Forbidden" when it tries to check if you are up to date.
>
> Can you tell me (privately, if you like) what User-Agent: it should present? Or suggest another mechanism to allow it access?
>
next prev parent reply other threads:[~2024-03-26 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98694616-5c5a-4edb-8e20-f1eaa4557542@me.com>
2024-03-26 12:01 ` Jon Turney
[not found] ` <bd369580-fe99-48b3-a441-08ab9fe893bb@me.com>
2024-03-26 17:40 ` Jon Turney
2024-03-26 18:13 ` Christopher Meng [this message]
2024-03-26 20:05 ` Kaz Kylheku
2024-03-27 2:40 ` Christopher Meng
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7475E6CC-779B-499D-AD51-A50FE2AA98CE@cicku.me \
--to=i@cicku.me \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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.
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).