[ale] Google resets

David Tomaschik david at systemoverlord.com
Mon Aug 20 19:01:41 EDT 2012


On Mon, Aug 20, 2012 at 2:45 PM, Scott Plante <splante at insightsys.com> wrote:
> Note that in last week's discussion, the symptom was Google giving a message
> about possible abuse and requiring a CAPTCHA once. So connection resets
> wouldn't be related to that problem. Also, as an added data point, I didn't
> have any problems with my Google searches this morning. Going to
> "google.com" in Chrome redirects to 'https://" for me. This may be because I
> have a saved Google login, or that I'm signed into it in Chrome.
>
> Scott

http://googleblog.blogspot.com/2011/10/making-search-more-secure.html

tl;dr: Google redirects all search traffic for logged-in users to HTTPS.

David

(And, as Aaron pointed out, I do work for Google, but of course am
only speaking for myself, and am not speaking as a representative of
Google.)


> From: "Jeff Lightner" <JLightner at water.com>
> To: "Atlanta Linux Enthusiasts" <ale at ale.org>
> Sent: Monday, August 20, 2012 11:26:50 AM
>
> Subject: Re: [ale] Google resets
>
> You really ought to read the entire email before you respond.  I made it
> clear I had already seen the earlier discussion.   My post was to see if
> anyone was having an issue TODAY and also a mini-rant against a practice
> that would cause this based on the reasoning given in that earlier
> discussion.
>
> Anyway it turns out my issue is that the default search engines in Firefox
> for some reason now uses https:// for Google rather than simple http:// - on
> doing the standard page in Firefox it works fine.
>
> Now the question is why does Firefox only have this https version when they
> clearly call it "experimental" in their discussion when you check for
> available search engines?  Another question would be does https normally
> work and it is just this part that Google is having issues with today?
> Anyone else able to get to Google via https?
>
> I'd actually seen similar issues a few weeks ago but didn't realize it was
> because their "default" was doing https://.   Since it was a side issue I
> didn't delve into it and later was no longer experiencing it.   This may be
> an issue with our internal web filter appliance.
>
>
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>



-- 
David Tomaschik
OpenPGP: 0x5DEA789B
http://systemoverlord.com
david at systemoverlord.com


More information about the Ale mailing list