Andrea Briganti

I think that the real problem is the activation from the google script. Did you tried to use the explicit version and to call the activation call after the ajax...

`{% recaptcha_init %}` is only a helper to make simpler to include the google script in your project. Only the explicit init is more complicated. I didn't understand what you...

@Bishwas-py it's the second time that you pollute a bug report with your article, that's not related to this package. please stop it.

The scope of RECAPTCHA_DISABLE is only for testing purpose and RECAPTCHA_PUBLIC_KEY and RECAPTCHA_PRIVATE_KEY are mandatory if you want to use django-recaptcha3. Why you need to use RECAPTCHA_DISABLE outside automated tests?

If you check how the widget is made, also if you can set an empty `RECAPTCHA_PUBLIC_KEY` you will create more problems than you want to solve, because you will get...

If you use `RECAPTCHA_DISABLE` you can also set dummy values for `RECAPTCHA_PUBLIC_KEY` and `RECAPTCHA_PRIVATE_KEY`. ``` RECAPTCHA_PRIVATE_KEY = 'dummy' RECAPTCHA_PUBLIC_KEY = 'dummy' RECAPTCHA_DISABLE = 'True' ``` It is not enough?

Yes I agree. If you would like to submit a PR about this topic I will be very happy.

Just a question, why you want to use a proxy only for recaptcha requests? You can always set the proxy when you run your Django app with environment vars: ```...

You don't need a proxy, because you need to change the url used by frontend and backend only. For the frontend I've added a configuration key, but I think that...

Reopened because I'm adding the proxy support also on the backend