Mirror prober fails to detect SSL error + 404 on a mirror with https redirection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
New
|
Undecided
|
Unassigned |
Bug Description
The owner of a mirror contacted us as their old mirror is still considered valid by the mirror prober while it has been out of date for months.
https:/
http://
For example the log says:
Wed Jan 4 16:59:49 2023: Found that http://
While:
$ curl -fIL http://
HTTP/1.1 301 Moved Permanently
Server: nginx/1.20.1
Date: Wed, 04 Jan 2023 23:41:39 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive
Location: https:/
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https:/
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
$ curl -fLIk http://
HTTP/1.1 301 Moved Permanently
Server: nginx/1.20.1
Date: Wed, 04 Jan 2023 23:44:56 GMT
Content-Type: text/html
Content-Length: 169
Connection: keep-alive
Location: https:/
HTTP/1.1 404 Not Found
Server: nginx/1.20.1
Date: Wed, 04 Jan 2023 23:44:57 GMT
Content-Type: text/html
Content-Length: 153
Connection: keep-alive
curl: (22) The requested URL returned error: 404
Thank you
Another report of outdated mirrors: /answers. launchpad. net/launchpad/ +question/ 704999
https:/
```
Hi,
https:/ /launchpad. net/ubuntu/ +mirror/ mirrors. xservers. ro-archive is wildly out of date (nothing after Focal), and yet as I'm typing this, it's still marked as Official. The log of the last probe is available at https:/ /pastebin. ubuntu. com/p/qZk3bKsFR B/.
I'm marking this mirror Unofficial now.
```