Thanks for the information.
I've used breakpoints before, but for this issue, it was happening on a
computer where I did not have the compiler, so I wanted something compiled into
the program that I could run on the computer with the issue and get the
backtrace information.. it worked great.
J
https://freepascal.org/
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
You probably want to give a bit more context here.
1. The error seems to be visible only in Safari (iOS or macOS).
I did test Chrome, it fails to open "https://freepascal.org"; and
automagically reopens "www.freepascal.org". Thus the certificate error is
not observed.
Chrome also suggested that re
Dmitry Boyarintsev via fpc-pascal wrote on 5/1/22 12:17 pm:
You probably want to give a bit more context here.
1. The error seems to be visible only in Safari (iOS or macOS).
You can add the SeaMonkey web browser on FreeBSD to the list.
___
fpc-pasc
You can add Firefox on Windows 10 which also sees this error.
Seems not to be a browser issue. If the user requests an https: connection, the
website should NOT revert to a http: connection. Instead it should return an
error if the https: connection cannot be made.
On Tue, 04 Jan
Hi,
Στις 5/1/2022 2:00 π.μ., ο/η Rainer Stratmann via fpc-pascal έγραψε:
https://freepascal.org/
the certificate issued for www.freepascal.org and not for freepascal.org .
It seems that the let's encrypt script was run with -d freepascal.org
instead of -d *.freepascal.org .
See https://www
