Page 1 of 1

httpsDefWhitelist blocks SeaMonkey update

Posted: Mon Jul 31, 2017 9:17 pm
by barbaz
SeaMonkey 2.48 is officially released, but updating to 2.48 needs to be done manually - https://www.seamonkey-project.org/news#2017-07-31

NoScript's httpsDefWhitelist feature, which I disable, is preventing users from updating. http://forums.mozillazine.org/viewtopic ... #p14758374

The solution here is to not force HTTPS for download.cdn.mozilla.net. Can this please be made default?

Re: httpsDefWhitelist blocks SeaMonkey update

Posted: Tue Aug 01, 2017 12:31 am
by therube
IMO, FWIW, the issue is with SeaMonkey - the particular URLs they are using to serve downloads.

And this is nothing new.
(At the least, SeaMonkey 2.46 was the same way.)

http://logs.glob.uno/?c=mozilla%23seamo ... 17#c699582

(The links in the log were automatically "hot linked" & in doing so, the http: or https: is "hidden", so you'll have to mouse-over the link to get a feel for the [confusing] issue.)

The solution here is to not force HTTPS for download.cdn.mozilla.net. Can this please be made default?
If that were done, that should work, I would think.
And once SeaMonkey gets their end together (pointing to download-installer.cdn.mozilla.net), then that (as https:) should just work too.

Actually I guess there is no reason at all for download.cdn.mozilla.net to be forced, as there is no certificate to be found there, so forcing it will never work - for anyone, any product.