Switch the download page to HTTP instead of FTP

[allanjude]

Summary

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200327

Note: we should create a new CNAME or something so that the url is not http://ftp.freebsd.org/ but rather http://download.freebsd.org due to Safari bugs etc.

[trasz]

Note there is/was a PR for this, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200327. I don't understand our mirror structure, so I don't know if this change won't break some of them.

[gavin]

Yeah, let's get download.freebsd.org into DNS and just use that straight off. Let me see if I can get that in place today.

[bcr]

I'm fine with the documentation part of the change.

[allanjude]

Update the download links to use the new download.freebsd.org alias with TLS

[allanjude]

mention https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200327 in commit

[gavin]

Can we hold off on this for now please? We're still deciding on exactly the layout of that site - i.e. whether "/pub" will be in the URL for example.

[allanjude]

No problem.

[trasz]

Ping?

[allanjude]

In D3754#89953, @trasz wrote:

Ping?

I think Gavin said this is ready to go now, they were just deciding on how to structure the URLs.

[trasz]

So, what needs to happen for this... to happen?

[allanjude]

Updated with new URLs

[allanjude]

Would it be possible to change the 'max width' of the filenames in the auto-generated index?

https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/11.0/

In the names of the snapshots, the end of the filename is cut off, and this is important, as it is where the 'type' of image is (memstick vs dvd etc)

[wblock]

In D3754#93308, @allanjude wrote:

Would it be possible to change the 'max width' of the filenames in the auto-generated index?

https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/11.0/

In the names of the snapshots, the end of the filename is cut off, and this is important, as it is where the 'type' of image is (memstick vs dvd etc)

In D3754#93308, @allanjude wrote:

Would it be possible to change the 'max width' of the filenames in the auto-generated index?

https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/11.0/

In the names of the snapshots, the end of the filename is cut off, and this is important, as it is where the 'type' of image is (memstick vs dvd etc)

Do we generate that with some script, or is it auto-generated by the web server? If it's a script, it doesn't appear to be in htdocs.

[allanjude]

Do we generate that with some script, or is it auto-generated by the web server? If it's a script, it doesn't appear to be in htdocs.

It is auto-generated by the web server. Depending on the web server, you can adjust it with some configuration directives, but I am not sure what web server is used.

[bcr]

Can someone from clusteradm@ help out with the webserver config, which seems to be the only showstopper now?

[lwhsu]

In D3754#108835, @bcr wrote:

Can someone from clusteradm@ help out with the webserver config, which seems to be the only showstopper now?

We can set this in nginx.conf:

fancyindex_name_length  100

to redefine the maximum file name length limit, patch has been sent to clusteradm@

[lwhsu]

BTW, I also found some other links might need changing: https://people.freebsd.org/~lwhsu/patch/download.diff

[peter]

fancyindex_name_length is now set to 100 and will propagate in a few minutes.

The things from lwhsu's diff are machine generated; the source should be changed for those.

[lwhsu]

In D3754#151727, @peter wrote:

fancyindex_name_length is now set to 100 and will propagate in a few minutes.

It seems work fine on all mirrors but not twn:
http://ftp0.twn.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/11.0/
config is not propagated in that colo, @peter ,could you help to check this?

[lwhsu]

@peter has fixed this. So I think this patch is good to be merged?

[lwhsu]

All mirror sites are working perfectly, I think there is nothing blocks this patch, right?

[allanjude]

This change is waiting until the 11.0 release cycle is over

[bcr]

Now that the 11.0 release cycle is finally over, can we move on with this?

[lwhsu]

I believe it is fine to land this change. Is there any other concern?

[emaste]

@allanjude, will you commit it now?

[lwhsu]

@allanjude ping?