I require a Perl script that acts as a transparent HTTP proxy and will intercept requests to Google Search that result in a captcha? and instead of? passing the response back to the requesting application, will instead pop up with a? Tk box showing the captcha image and allowing the user to? unlock it.? In that case the proxy will respond to the captcha challenge? (without the original application knowing that this is happening) and return the final search results back to the requesting application.
This should be built? in a modular? fashion? so that other? captcha's can be similarly intercepted later? on.
?
## Deliverables
| ****![][1] Brief Summary:**
**
* Rent A Coder reminder: You MAY NOT post the final solution for this (and any) project before your bid is accepted and funds are fully escrowed. Anyone who does may have their account permanently suspended. However, you CAN post:
* On programming projects: A prototype or functional demo...as long as source code is not provided.
* On graphics projects: A watermarked and low-resolution version of the work.
I need a tool that will? sit in the system tray, intercept HTTP requests made to search engines (at least Google and Yahoo) which get Captcha pages, and when found, display the captcha and send the request back to the search engine to unlock the search.
This should be completely transparent to software running on the system - no software should need to do anything to utilize this (unless you can convince me that this is impossible, which I find hard to believe because there are HTTP protocol inspectors that can change requests/responses on-the-fly).? Also software making a request that triggers the captcha shouldn't even see the captcha response; this software should catch that and all the software making the request will see is the final response (after being unlocked)
**![][2] Requirements Interview Answers: ![][3]**
To help you bid more accurately, the buyer was interviewed about the requirements for this project. Below are their answers. ![][4] **Other Requirements:**
This must catch Google searches that get 302-ed to [login to view URL] and distinguish between searched that go to a captcha page, and searches that are completely blocked (like? <[login to view URL]://[login to view URL]>? )
The application must be somewhat modular so that additional captchas can be detected/intercepted in the future.?
There should also be a cancel button on the popups which will pass the captcha page back to the application that made the request instead of trying to unlock it ourselves.
Also, it should be designed to not need to be triggered multiple times, if not needed; so if we can avoid multiple popups by, say, storing (or NOT storing) a cookie, then we should have an option to forcefully inject (or remove) the cookie from subsequent requests from the same process that originally triggered the captcha (or shared across all processes - you tell me what will work best) |