v 11.0.9rc1
============================================================
[...]
x Use invalid IP rather than domain name to prevent offline
status from breaking sync messaging in Chromium
I am uncertain enough about this that I'm keeping NoScript at 11.0.8rc1 until I better understand the consequences of this change. Thanks for any clarification.
*Always* check the changelogs BEFORE updating that important software!
barbaz wrote: ↑Sun Nov 17, 2019 12:10 am
In my experience, using 255.255.255.255 as a "invalid IP" can actually result in connection attempts, whereas using 0.0.0.0 seems not to.
What's your experience exactly?
My experience: in Firefox and Chromium (on Linux at least), http://0.0.0.0 opens the web server on localhost, while http://255.255.255.255 fails as an invalid address before any connection attempt.
barbaz wrote: ↑Sun Nov 17, 2019 12:10 am
1) Why use 255.255.255.255 instead of 0.0.0.0?
barbaz wrote: ↑Sun Nov 17, 2019 12:10 am
In my experience, using 255.255.255.255 as a "invalid IP" can actually result in connection attempts, whereas using 0.0.0.0 seems not to.
What's your experience exactly?
My experience: in Firefox and Chromium (on Linux at least), http://0.0.0.0 opens the web server on localhost, while http://255.255.255.255 fails as an invalid address before any connection attempt.