[177421] in North American Network Operators' Group
Re: HTTPS redirects to HTTP for monitoring
daemon@ATHENA.MIT.EDU (Geoffrey Keating)
Sun Jan 18 15:51:41 2015
X-Original-To: nanog@nanog.org
To: chris <tknchris@gmail.com>
From: Geoffrey Keating <geoffk@geoffk.org>
Date: 18 Jan 2015 12:49:10 -0800
In-Reply-To: <CAKnNFz8Q87ORf9c0HBz2AV_9-DjT-oOfrgG3uHdgujJAz+P=-Q@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
chris <tknchris@gmail.com> writes:
> I have been going through something very interesting recently that relates
> to this. We have a customer who google is flagging for "abusive" search
> behavior. Because google now forces all search traffic to be SSL, it has
> made attempting to track down the supposed "bad traffic" extremely
> difficult. We have contacted google through several channels and no one at
> google who we've worked with is able to provide us any factual examples of
> what they are seeing and because of the traffic being encrypted all our
> usual capture and analysis tools have been fairly useless.
I presume the problem is that Google has flagged the outgoing address
on your NAT, because that's all they can see.
Have you considered deploying IPv6 and giving each customer their own
address? Then only that customer will be flagged and it'll be between
them and Google.
