The GoogleProxyBlocker, or GPB for short, has just been released. It's bloody fast, gets the job done, and can be quickly configured. Read about it here.
If you're not yet paranoid about Google's Web Accelerator, try the following
links:
Google
Web Accelerator Has Security Issues.
Google
Accelerator Deleting by Prefetching.
Google
Web Accelerator considered overzealous.GWA ruined my
marriage, ate my kittens, and made me lose my job.
(Well, that last link might be bogus.)
Anyhow, check it out. This will be something handy to know about down the road if the GWA doesn't choke on a chicken-bone here in the next few days.
This is really cool. I see that google has pulled it down now - no mention in the tools section at all anymore. That means that I have to rely on all the articles out there for technical info, but most are just talking in vague generalities. I don't care about the GET part - I don't think I've ever used a link to alter information - but I am concerned by rumors that people could view a site and be signed in as someone else. Using Forms Authentication that has to be BS, right? I mean, they don't cache other peoples cookies, surely?
Posted by: James Shaw | May 10, 2005 at 08:09 AM
Very cool. Thank you. What do we do if we're still running classic asp? Or even, gasp! php? I hope Google pulls the plug on this one.
Posted by: Jon Sharp | May 10, 2005 at 08:35 AM
James, Glad you liked the site. Also glad that Google pulled that pig down. I'm pretty sure they don't cache cookies. That would be obtuse. Then again, writing a proxy for dynamic web content is obtuse too. I had ooodles of visitors to my site yesterday due to the release of my GPB 1.0. If Google were allowed to proxy those hits, I'd have no clue how many people were coming to my site etc. This is mostly just a hobby site, so imagine if you were trying to run a business, sent out an email about your latest widget to your customer base, and only got 4 click backs (because google was proxying your site). I just hate this proxy thing. Seriously, as a developer I can 100% state that proxies are evil. All developers hate them -- they cause all sorts of issues.
Posted by: Michael K. Campbell | May 10, 2005 at 09:10 AM
Jon, There have been a number of fixes posted on Apache/PHP sites. If you were in classic ASP... I'd say just make an #include and drop it in all the files you needed to cover (more of a pain that just dropping in a single HttpModule).
Posted by: Michael K. Campbell | May 10, 2005 at 09:12 AM