On 06/01/2012 12:21 PM, JC Dill wrote:
> I'm running into a problem where it looks like https is being blocked,
> but only on one network I'm using. (Arugh!) I think I may also have
> https everywhere enabled, as attempts to reach pages like
>
http://maps.google.com redirect to
https://maps.google.com, and since
> https is blocked, I can't reach Google Maps.
Works for me.
Build identifier: Mozilla/5.0 (X11; Linux i686; rv:12.0)
Gecko/20120429 Firefox/12.0 SeaMonkey/2.9.1
[HTTPS-Everywhere 2.0.5]
And
User Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101
Firefox/12.0
[
HTTPS-Everywhere2.0....@eff.org]
And
Safari 5.0.5 (7533.21.1)
Note: no https everywhere installed on that as there isn't a version for
Safari (that I'm aware of) - I just tried '
https://google.maps' instead.
My _guess_ is that it's not https that is causing you problems if you
can't get to '
https://google.maps' from Safari.
>
> I'd like to disable https everywhere, but I can't reach the EFF page
> about https everywhere - because https is being blocked. Catch-22! I
> tried using Yahoo cache, but it just redirects to the eff site (using
> https) so I can't actually SEE the cache page.
>
> Can someone look-up the info about how to disable https everywhere for
> both Safari and Firefox, on a Mac?
Firefox:
about:addons
Or Tools|Add-ons
HTTPS Everywhere - Disable
(however you might want to check Preferences
>
> Or... is there some other reason that attempts to reach
>
http://maps.google.com would be redirected to
https://maps.google.com
> which then doesn't work? (In other words, have I made a dumb assumption
> about where the root problem lies?)
>
> jc
I modified my Google search button a long time ago to use https
(
https://encrypted.google.com/), I I use it even if I do not have
https-everywhere turned on.
As a side note: When in Safari, I decided to try the 'Help|Safari
Extensions Gallery' to see if perhaps there was an 3rd party
https-everywhere... had to laugh as that came up with an invalid cert
error. However, going back to the link is fine & uses the proper
Verisign cert.