Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.utanet.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail
Newsgroups: comp.lang.java.programmer
From: Andreas Leitgeb <avl@gamma.logic.tuwien.ac.at>
Subject: Re: proxy baffement
References: <qefbc75va1lc98u1i4db78eo4ipcmeeeeh@4ax.com>
Reply-To: avl@logic.at
User-Agent: slrn/pre0.9.9-111 (Linux)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <slrnjcf3ls.fvg.avl@gamma.logic.tuwien.ac.at>
Date: 19 Nov 2011 11:10:52 GMT
Lines: 11
NNTP-Posting-Host: gamma.logic.tuwien.ac.at
X-Trace: 1321701052 tunews.univie.ac.at 60386 128.130.175.3
X-Complaints-To: abuse@tuwien.ac.at
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10065

Roedy Green <see_website@mindprod.com.invalid> wrote:
> I fired up Wireshark to see if I could figure out what was going on.
> The first thing I noticed was this
> GET
> /tbproxy/lh/fixurl?hl=en-US&sd=ca&url=http%3A%2F%2Fask.com%2F&sourceid=chrome&error=connectionfailure
> HTTP/1.1
> Host: linkhelp.clients.google.com

Another thing: I googled for "tbproxy fixurl" and got hits mostly talking
about some google-script to be used for a site's 404-page.