30 Jul
2025
30 Jul
'25
1:44 a.m.
Could be. But I suspect it might just be because people tend to not
explicitly tell which protocol to use, and they might now default to
https, and then try http if that didn't work.
So just try to explicitly say http://mim.softjar.se/ and see if things
don't become happier...
Johnny
On 2025-07-30 01:36, Terri Kennedy wrote:
On 2025-07-29 19:15, Johnny Billquist wrote:
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
And now I see what you guys were/are doing.
You're trying to use https. I don't have any https server, and when
you try that, you are essentially repeatedly hitting a port that do
not provide any service, and eventually you get blocked.
Stop trying to use https against Mim. :-D
Many people don't have a choice. Browsers try HTTPS auto-
matically and then fall back to HTTP if there's nobody home
on 443.
This is part of "Browsers are considered feature-complete,
so all we can do is keep rearranging the layout, dropping
FTP, and deciding that forcing people to use no crypto in-
stead of bad crypto is always a Good Thing" (not!) See:
Is no crypto always better than bad crypto?
https://www.glaver.org/blog/?p=853
Is no crypto always better than bad crypto (Part 2)?
https://www.glaver.org/blog/?p=1768
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se