I guess the issue was with IPv6 routing:
$ wget https://hg.savannah.gnu.org/hgweb/octave
--2023-04-12 11:07:19-- https://hg.savannah.gnu.org/hgweb/octave
Resolving hg.savannah.gnu.org (hg.savannah.gnu.org)... 2001:470:142:5::201,
209.51.188.201
Connecting to hg.savannah.gnu.org
(hg.savannah.gnu.org)|2001:470:142:5::201|:443...
failed: Connection timed out.
Connecting to hg.savannah.gnu.org (hg.savannah.gnu.org)|209.51.188.201|:443...
connected.
HTTP request sent, awaiting response... 200 Script output follows
Length: unspecified [text/html]
Saving to: ‘octave’
octave [ <=>
] 18.96K --.-KB/s in 0.001s
2023-04-12 11:09:29 (17.8 MB/s) - ‘octave’ saved [19410]
I rebooted my router and now it looks OK:
$ wget --verbose https://hg.savannah.gnu.org
--2023-04-12 11:27:51-- https://hg.savannah.gnu.org/
Resolving hg.savannah.gnu.org (hg.savannah.gnu.org)... 2001:470:142:5::201,
209.51.188.201
Connecting to hg.savannah.gnu.org
(hg.savannah.gnu.org)|2001:470:142:5::201|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 1492 (1.5K) [text/html]
Saving to: ‘index.html’
index.html
100%[==========================================================>] 1.46K
--.-KB/s in 0s
2023-04-12 11:27:52 (63.3 MB/s) - ‘index.html’ saved [1492/1492]
Not sure why chrome would work -- does it force name resolution to IPv4?
Anyway, it is all good now.
Thanks.
Dmitri.
--
On Wed, Apr 12, 2023 at 11:20 AM Corwin Brust <cor...@bru.st> wrote:
> Hi Dmitri!
>
> On Wed, Apr 12, 2023 at 9:44 AM Dmitri A. Sergatskov
> <dasergats...@gmail.com> wrote:
> >
> > I cannot access https://hg.savannah.gnu.org/hgweb/
> > with either "hg" or "wget" or "lynx",
> > but can with chrome browser. E.g.:
>
> Hmm, I'm able to access via wget:
>
> $ wget -O - https://hg.savannah.gnu.org/hgweb/
> [... reasonable looking HTML snipped ...]
> 2023-04-12 10:17:55 (774 KB/s) - written to stdout [79529]
>
> I do not believe it is filtering by User-Agent.
>
