You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HTTP URLs opened from bookmarks should not be upgraded to HTTPS #17
This is due to limitations of the extension API. For bookmarks I could try to detect whether a host name is bookmarked, and if if so, if there is at least one https-URL before redirecting.
For the case of non-bookmarked domains, there is no side channel that I can use to determine whether the user typed "http://" or nothing.
Would the ability to forcidbly navigate to http (e.g. typing "h example.com" -> "http://example.com") be a good option for you?
@cben That bug hasn't been closed yet. Though even if the linked bugs get resolved (i.e. we can distinguish typed navigations from non-typed navigations), then we still have the problem of detecting typed example.com from typed http://example.com.
I'm starting to suspect that perhaps the best way to replicate the original behaviour would be to use the code from the original add-on to make a patch in gecko directly (behind an about:config pref).
BTW, another useful extension to create would be one that goes through all bookmarks and sees if https is available for them. The only trick is that a screenshot would have to be taken of both the http and https versions to compare them. Some sites will load on https, but the content is broken.
This is something that can easily be done with an extension. But instead of using a screenshot, I would suggest to just confirm that the request succeeds successfully, or at most compare the response text. Comparing by screenshots is complicated and easily defeated when the result has dynamic content, e.g. embedded adverts.
Activity
fmarier commentedon Dec 22, 2017
Actually, the problem seems larger than the above scenario.
On 0.4.3, if I do the following
then I am taken to "https://example.com" instead of "http://example.com".
Rob--W commentedon Dec 22, 2017
This is due to limitations of the extension API. For bookmarks I could try to detect whether a host name is bookmarked, and if if so, if there is at least one https-URL before redirecting.
For the case of non-bookmarked domains, there is no side channel that I can use to determine whether the user typed "http://" or nothing.
Would the ability to forcidbly navigate to http (e.g. typing "h example.com" -> "http://example.com") be a good option for you?
cben commentedon Dec 22, 2017
Rob--W commentedon Dec 22, 2017
@cben That bug hasn't been closed yet. Though even if the linked bugs get resolved (i.e. we can distinguish typed navigations from non-typed navigations), then we still have the problem of detecting typed
example.comfrom typedhttp://example.com.fmarier commentedon Dec 22, 2017
I'm starting to suspect that perhaps the best way to replicate the original behaviour would be to use the code from the original add-on to make a patch in gecko directly (behind an about:config pref).
Rob--W commentedon Dec 31, 2019
(this is off-topic)
This is something that can easily be done with an extension. But instead of using a screenshot, I would suggest to just confirm that the request succeeds successfully, or at most compare the response text. Comparing by screenshots is complicated and easily defeated when the result has dynamic content, e.g. embedded adverts.
To get started with developing extensions, see https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions
and for your specific use case, see https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Work_with_the_Bookmarks_API