[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
wget2 | Crawling fails, when https is on non-standard port (#645)
From: |
linuxd3v (@linuxd3v) |
Subject: |
wget2 | Crawling fails, when https is on non-standard port (#645) |
Date: |
Sun, 24 Sep 2023 21:55:24 +0000 |
linuxd3v created an issue: https://gitlab.com/gnuwget/wget2/-/issues/645
The below wget2 command fails to crawl the site, however works just fine if
address is just ex: https://example.com
```bash
wget2 --recursive \
--no-parent \
--level=5 \
--tries=3 \
--timeout=11 \
--spider \
--delete-after \
--header "Accept-Encoding: gzip, deflate, br" \
--user-agent=bp-warming-client \
--secure-protocol=TLSv1_3 \
--limit-rate=0.5M \
--domains=https://hs-dev1.example.com:31756 \
https://hs-dev1.example.com:31756
```
0 files 100%
[====================================================================>] 414
--.-KB/s
[Headers: 3 (3 redirects & 0 errors) Bytes: 0 [0
B/s] Todo: 0 ]
I suspect it's because the domain is configured with TLS on :31756 as opposed
to standard :433? but have nothing more to go off.
wget2 --version
GNU Wget2 2.1.0 - multithreaded metalink/file/website downloader
--
Reply to this email directly or view it on GitLab:
https://gitlab.com/gnuwget/wget2/-/issues/645
You're receiving this email because of your account on gitlab.com.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- wget2 | Crawling fails, when https is on non-standard port (#645),
linuxd3v (@linuxd3v) <=