TeX Live future access in danger

[Markus Kohm]

Am Samstag, 13. April 2019, 03:34:17 CEST schrieb George N. White III:
> Existing links in documents on the server will still have HTTP URL's, so
> in practice, CTAN sites have to provide HTTP for the foreseeable
> future.

This is usually solved by redirecting. E.g., if you try http://
www.komascript.de/node/1801 you will be redirected to https://komascript.de/
node/1801 automatically:

Resolving www.komascript.de (www.komascript.de)... 2a01:238:43fc:
2300:6350:9cb2:8bae:dfe6, 85.214.222.242
Connecting to www.komascript.de (www.komascript.de)|2a01:238:43fc:
2300:6350:9cb2:8bae:dfe6|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://komascript.de/node/1801 [following]
--2019-04-13 09:37:28--  https://komascript.de/node/1801
Resolving komascript.de (komascript.de)... 2a01:238:43fc:
2300:6350:9cb2:8bae:dfe6, 85.214.222.242
Connecting to komascript.de (komascript.de)|2a01:238:43fc:
2300:6350:9cb2:8bae:dfe6|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: '1801.'

This shouldn't be a problem in the webserver configuration. The only problem
are clients that do not support https. They cannot reach the site and this is
intended.

Markus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <https://tug.org/pipermail/tex-live/attachments/20190413/fd55180d/attachment-0001.sig>