You are not logged in.
Pages: 1
Hi,
I have an Archlinux installation script that installs "snapshots" of a specific date using the Archlinux Archive. I'm using a HTTP-proxy in order to save bandwidth. Recently my script stopped working, and when I investigated, I found that http://archive.archlinux.org now redirects to https://archive.archlinux.org/. Does anybody know the reason for this switch? The packages are signed anyway, so what's the benefit of enforcing https?
Best,
Jan
Offline
What's the benefit of *not* using https? There are good arguments that all web traffic should now only be over https. I'm not well versed enough to critically evaluate those arguments, but I find them compelling and have moved every site I maintain to https only (with proper http redirects).
Is there a reason this would be a problem? If curl is failing, either add the 's' or include "-L" in curl flags (often a good idea in scripts anyways).
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
One big benefit of using plain HTTP is the ability to use a caching proxy.
Offline
Pages: 1