Well the users are able to see the CAPTCHA image that is not the
problem. The problem occurs on the server side when the CAPTCHA
verification is called by the server which sends its request through
the firewall without any proxy info. This causes the firewall to drop
the CAPTCHA packets.
My networking guys are telling me, we need to some how call this
request through the proxy server so it can go through or we would have
to open up all of google through the firewall. I dont think the second
option is something we are willing to do.
- Murtaza
On Jul 13, 10:13 am, PJH <
pauljherr...@gmail.com> wrote:
> About the only concession that I'm aware of that you can make is documented
> athttp://
code.google.com/p/recaptcha/wiki/FirewallsAndRecaptcha.
>
> Somehow or other the server running your requests needs to access the
> reCAPTCHA servers, in addition to the client's. If you're going to set up
> Squid, for example, then you'll have to make sure it uses pass-through and
> not cache anything to do with reCAPTCHA.
>
> Presumably your users are able to access the internet (otherwise they
> wouldn't be able to see the image to begin with) - what's the particular
> problem with the server they're using also being allowed to?
>
>
>
>
>
> On Wed, Jul 13, 2011 at 3:06 PM, Murtaza <
pubo...@gmail.com> wrote:
> > Is there a way to provide proxy info for RECAPTCHA to make the
> > verification request? This is turning into a big security issue for us
> > because essentially we have to open up request to the qualified domain
> > name which iswww.google.comif we cant specify a proxy for this