On 2025-08-19 01:41:36 +0200, Steffen Nurpmeso wrote: > P.S.: i really think it is on purpose, but i could not find the > context where he mentioned it; he cares for elder machines which > cannot do TLS, if i recall correctly.
For http://gcc.gnu.org at least: qaa:~> wget http://gcc.gnu.org --2025-08-19 03:20:42-- http://gcc.gnu.org/ Resolving gcc.gnu.org (gcc.gnu.org)... 2620:52:3:1:0:246e:9693:128c, 8.43.85.97 Connecting to gcc.gnu.org (gcc.gnu.org)|2620:52:3:1:0:246e:9693:128c|:80... connected. HTTP request sent, awaiting response... 302 Found Location: https://gcc.gnu.org/ [following] --2025-08-19 03:20:43-- https://gcc.gnu.org/ Connecting to gcc.gnu.org (gcc.gnu.org)|2620:52:3:1:0:246e:9693:128c|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 19956 (19K) [text/html] [...] As you can see, there is a forced redirect to https, so older machines that do not support https will not be able to access the GCC website anyway. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
