phkb wrote: ↑Wed Oct 11, 2023 8:35 am
I just tried using the download manager in Oolite, which was able to download a catalog (although it did say, briefly, that the file size was something ridiculous - a detail that didn't prevent the catalog downloading). Everything looks ok-ish (there obviously a lot of missing info URL's), but the "Asteroid Tweaks" OXP is flagged on my system as "Installed but no longer available for download". It's the only one flagged this way. OoliteStarter, however, says it's Online and Installable. I checked the download URL in the and the file is at the designated location. So not sure what is going on here. Unless we are not confident that the Oolite Expansion Manager is working at the moment.
Asteroid Tweaks as OXP or Asteroid Tweaks as OXZ? OXPs do not have a download URL per definition. An OXZ might get expanded into the AddOns folder to allow modifications. At that moment the versioning is broken. Or should we see a bug? Let's track this down.
As I do not have that expansion installed (neither as OXP nor as OXZ) it is shown as Online and Installable.
phkb wrote: ↑Wed Oct 11, 2023 8:35 am
I'm also still confused by the upload_date. You said:
hiran wrote: ↑Wed Oct 11, 2023 7:11 am
But as the scanner is not just triggered on repo changes but also regularly, sooner or later the scanner will access the expansion. Metadata is extracted and put into the catalog, and the Last-Modified header is taken as the upload_date.
With the Manual Witchspace Alignment OXP, it is still showing as 1/1/1970 (ie no upload date), although it was picked up as a changed file in index.html. Or is another process at work that will update the upload date?
In our expansions list we have:
https://github.com/OoliteProject/oolite ... s.txt#L170
and I find the URL
http://wiki.alioth.net/img_auth.php/8/8 ... gnment.oxz
Code: Select all
$ curl -v -X HEAD http://wiki.alioth.net/img_auth.php/8/8b/ManualWitchspaceAlignment.oxz
Warning: Setting custom HTTP method to HEAD with -X/--request may not work the
Warning: way you want. Consider using -I/--head instead.
* Trying 109.70.41.29:80...
* Connected to wiki.alioth.net (109.70.41.29) port 80 (#0)
> HEAD /img_auth.php/8/8b/ManualWitchspaceAlignment.oxz HTTP/1.1
> Host: wiki.alioth.net
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.22.1
< Date: Wed, 11 Oct 2023 08:46:01 GMT
< Content-Type: text/html
< Content-Length: 169
< Connection: keep-alive
< Location: https://wiki.alioth.net/img_auth.php/8/8b/ManualWitchspaceAlignment.oxz
<
No Last-Modified header. Let's use the URL the response pointed us to:
Code: Select all
$ curl -v -X HEAD https://wiki.alioth.net/img_auth.php/8/8b/ManualWitchspaceAlignment.oxz
Warning: Setting custom HTTP method to HEAD with -X/--request may not work the
Warning: way you want. Consider using -I/--head instead.
* Trying 109.70.41.29:443...
* Connected to wiki.alioth.net (109.70.41.29) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=wiki.alioth.net
* start date: Aug 21 07:09:41 2023 GMT
* expire date: Nov 19 07:09:40 2023 GMT
* subjectAltName: host "wiki.alioth.net" matched cert's "wiki.alioth.net"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> HEAD /img_auth.php/8/8b/ManualWitchspaceAlignment.oxz HTTP/1.1
> Host: wiki.alioth.net
> User-Agent: curl/7.81.0
> Accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx/1.22.1
< Date: Wed, 11 Oct 2023 08:47:59 GMT
< Content-Type: application/zip
< Content-Length: 336249
< Connection: keep-alive
< X-Content-Type-Options: nosniff
< Last-Modified: Wed, 11 Oct 2023 05:14:33 GMT
<
And there you go: The expansion was uploaded at Wed, 11 Oct 2023 05:14:33 GMT
Usually you do not notice since many clients will follow the redirect implicitly. Maybe in your browser start the developer tools and watch the network traffic.
