What's new
  • Welcome to PHCorner forums. Take a moment to sign up and gain unlimited access and extra privileges that guests are not entitled to, such as: All that and more! Registration is quick, simple and absolutely free. Join our community today!

Tutorial Use Google as a Proxy.

Not open for further replies.


Eternal Poster
Apr 28, 2013

Google has enhanced our lives in all sorts of ways, with voice apps, mail, maps, and so on. But they also do the more mundane, such as Google Translate.

I've found that you can use You do not have permission to view the full content of this post. Log in or register now. as a sort of lazy man's proxy/filter avoidance. Where I work, we've got a web content filtering tool that, for the most part, blocks inappropriate content, but is most certainly not immune to false positives -- blocking stuff that's not in any way objectionable. Maybe it's blocking on something as stupid as a word found in a URL, say, if you wanted to learn about some birds. In my case, I was looking for some technical discussions related to my work, but my employer's network filtering app told me (erroneously) that it was a ******** site.

Step 1: Visit Google Translate


Go to You do not have permission to view the full content of this post. Log in or register now. and try feeding
You do not have permission to view the full content of this post. Log in or register now. for example.
You might try translating from English to Filipino or vice versa.

Step 2: What have we accomplished?


Of course we didn't really seem to accomplish anything by asking a translation service to not translate a webpage. But in truth, some of the content was proxied through Google's Translate service. Using the Firebug Extension for Firefox, I was able to see that the request to see the front page of Instructables.com through Google Translate resulted in 26 HTTP requests, and only 3 of them were sent directly to instructables.com (2 for JS, 1 for CSS). So, this isn't a bulletproof method of avoiding ALL requests to the "translated" domain, but most of the content did indeed go through Google's translation services.

But can we make it a bit easier to automate the usage of this tool? Maybe a little bookmarklet?

Step 3: The Handy Bookmarklet


I admit my bias to using FIrefox. I don't know whether this works in IE. However, we can create a "bookmarklet" using Javascript. My code is as follows:


Create a new bookmark on your bookmark toolbar, and in the "Location" field, paste the javascript code seen above. Give it whatever name you wish. Once you click on it, you should be prompted to enter the URL you want to view.

Step 4: The Caveats: Not a 100% perfect proxy.

As I mentioned in Step 2, this isn't a perfect proxy. You can see that some style and script requests went through to the original website. If you really, really wanted to, you could put the original site in a hosts file pointed to on your Windows PC, but that's beyond the scope of this Instructable, and wouldn't account for changes on the originating site, such as moving scripts and styles to a subdomain or other related site that is also blocked.

I must emphasize that since this isn't a bulletproof solution to getting around filtering, it's wise not to use this to access content that you're really not supposed to get to, especially if you've got parents, administrators or employers looking through their filtering/proxying logs. If you really want to visit Zombo.com or a taste of the original Hamster Dance, you'll have to do it on your own time from home.




hindi nito kaya i-unblock ung restricted sites sa office namin pero meron ako ishare sa inyo, meron ako ibang way para ma-unblock nyo yung mga restricted sites try nyo palitan ung dns server ng gamit nyo na unit try nyo gamitin google dns primary secondary sana makatulong sa inyo.

wag kayo matakot palitan dns server nyo pwede nyo naman iobtain ung original dns server nyo :)

thats it sana makatulong :)
Not open for further replies.

Online statistics

Members online
Guests online
Total visitors

Forum statistics

Profile posts