On Mon, Jul 29, 2024 at 10:09 PM Roland Giesler via Mailman-users < mailman-users@mailman3.org> wrote:
On 2024/07/29 16:26, Roland Giesler via Mailman-users wrote:
However, the response URL doesn't not respond when I click it. It opens in a browser, but the processes times out. I'm now checking why that is.
I found out why. Firefox and Brave (Chromium) have a bug in their https redirect functionality, so one cannot disable https redirection on any site at this stage. Since I don't have the https certificates in place, I had to use Edge to be able to visit
http://192.168.161.103/accounts/confirm-email/Mg:1sYQR2:xt3_639JwJ78GW9XhrpK...
Account verified.
The actual issue is that the verification email URL is sent with HTTPS://...... You cannot blame a browser for NOT respecting the HTTPS and redirecting it to HTTP. So one has to know that their site is not secured with SSSL certs, and so change httpS:: to http:// I don't think Edge is the only one that does that. On my tests, I use VMs and Brave/Chrome/Firefox to access the link. I just change HTTPs to HTTP manually. It's a situational awareness type of thing.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]