Path: ...!news.mixmin.net!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Mild Shock <janburse@fastmail.fm>
Newsgroups: comp.lang.prolog
Subject: Re: broken and insecure links (Was: comp.lang.prolog Frequently Asked
 Questions)
Date: Fri, 20 Sep 2024 10:59:34 +0200
Message-ID: <vcjdhl$dgun$1@solani.org>
References: <18c37160924.070003@logic.at> <vcja71$df34$1@solani.org>
 <vcjcco$g1tk$1@solani.org> <vcjcgo$g1tk$2@solani.org>
 <vcjcrc$g28h$1@solani.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 20 Sep 2024 08:59:33 -0000 (UTC)
Injection-Info: solani.org;
	logging-data="443351"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.19
Cancel-Lock: sha1:/L9LTdHIUoSzYDQOb/jgmy+NgdU=
X-User-ID: eJwFwYkBwEAEBMCWEIsrx9t/CZnBZ2ztajDF4WgxcZUcq/RK5kkvQaTRHBceztc3PV8upXKtS9b4Wb9N/QFs3xav
In-Reply-To: <vcjcrc$g28h$1@solani.org>
Bytes: 2408
Lines: 35

GIT does also produce a HTTPS warning and
not allow HTTP at all, it works with a HTTP
client that has redirect(true):

$ git clone http://www.dogelog.ch/dogelog/.git
Cloning into 'dogelog'...
warning: redirecting to https://www.dogelog.ch/dogelog/.git/
Fetching objects: 4613, done.

The warning tells me I have a **security glitch**
using initially HTTP, and I should use a HTTPS
link from the start.

Your SWI-Prolog GIT library might suppress this
warning, which is **not ok** in my opinion. To avoid
the warning I directly publish a HTTPS link:

1 GIT Access
For binary files and source code initially:
git clone https://www.dogelog.ch/dogelog/.git

Mild Shock schrieb:
> Here is a sketch how this could be checked:
> ```
>      http_open(_, _, [final_url(FinalURL)]),
>      (\+ sub_atom(FinalURL, 0, _, _, 'https:') ->
>             /* show some warning or even fatal error */
> ```
> [https://www.swi-prolog.org/pldoc/man?predicate=http_open/3](https://www.swi-prolog.org/pldoc/man?predicate=http_open/3) 
> 
> 
> Or better using the `redirect(false`) http option
> from the beginning. Some modern HTTP clients have
> even a third `redirect/1` option besides true and
> 
> false that prevents HTTP to HTTPS promotion.