The Google Translate recursion bug

Recently I found a bug in Google Translate. It’s not damaging, but it is interesting.

What I have discovered is that when you use a certain string, the Google Translate frame inserts itself into the main frame, causing it to load again within that frame, in turn this causes it to reload within that frame and this continues until your browser decides it’s had enough and stops (or in the case of Internet Explorer, until it locks up). This kind of self-looping is often referred to as recursion.

First off, I want to say point out that I did try and ask various people how to contact Google to report this bug, but nobody got back to me.

It seems nobody wants to take responsibility for the Google Translate project and I was all up for reporting it as I heard other people have received T-Shirts for doing so. But, no T-shirt for me, so I guess I’ll just publish on my site instead and see if they fix it.

Also last time I provided feedback to Google, they created a solution, but never emailed me back to thank me or anything. (The “Go to” that appears on the Google regional search (eg: Google UK) is a direct result of my feedback, it did not exist until about a month after I submitted my feedback).

Don’t get me wrong, I like Google, but it’s not nice to be ignored.

Okay, so onto the actual bug…

Google Translate Recusion

Google Translate Recursion

I discovered this after trying to translate a URL from a Wikipedia.

I narrowed this down to the apostrophe (‘) in the URL…’

I realised it would work on any domain…’

However, it did not, or does no longer work with just an apostrophe…

Bad Request
Your client has issued a malformed or illegal request.

Redirects to home page.

Interestingly enough though, it does work when translating Google’s very own search:

A pretty poor show by Google if you ask me.

I do wonder though, who will get there first? Will Google fix it or will someone exploit it?

There’s only one way to find out… Post!


Update 04-Sept-2009: It seems to me that this bug has been fixed. I await my Google T-shirt…