Django hCaptcha provides a simple way to protect your django forms using hCaptcha.
Configuration
Add “hcaptcha” to your INSTALLED_APPS setting like this:
INSTALLED_APPS = [
...
'hcaptcha',
]
For development purposes no further configuration is required. By default, django-hCaptcha will use dummy keys.
For production, you’ll need to obtain your hCaptcha site key and secret key and add them to you settings:
HCAPTCHA_SITEKEY = '<your sitekey>' HCAPTCHA_SECRET = '<your secret key>'
You can also configure your hCaptcha widget globally (see all options):
HCAPTCHA_DEFAULT_CONFIG = {
'onload': 'name_of_js_function',
'render': 'explicit',
'theme': 'dark', # do not use data- prefix
'size': 'compact', # do not use data- prefix
...
}
If you need to, you can also override default hcaptcha endpoints:
HCAPTCHA_JS_API_URL = 'https://hcaptcha.com/1/api.js' HCAPTCHA_VERIFY_URL = 'https://hcaptcha.com/siteverify'
Use proxies:
HCAPTCHA_PROXIES = {
'http': 'http://127.0.0.1:8000',
}
Change default verification timeout:
HCAPTCHA_TIMEOUT = 5
Usage
Simply add hCaptchaField to your forms:
from hcaptcha.fields import hCaptchaField
class Forms(forms.Form):
....
hcaptcha = hCaptchaField()
....
In your template, if you need to, you can then use {{ form.hcaptcha }} to access the field.
You can override default config by passing additional arguments:
class Forms(forms.Form):
....
hcaptcha = hCaptchaField(theme='dark', size='compact')
....
How it Works
When a form is submitted by a user, hCaptcha’s JavaScript will send two POST parameters to your backend, g-captcha-resposne and h-captcha-response. These will be received by your app and will be used to complete the hcaptcha form field in your backend code.
When your app receives these two values, the following will happen:
Your backend will send these values to the hCaptcha servers
Their servers will indicate whether the values in the fields are correct
If so, your hcaptcha form field will validate correctly
Unit Tests
You will need to disable the hCaptcha field in your unit tests, since your tests obviously cannot complete the hCaptcha successfully. One way to do so might be something like:
from unittest.mock import MagicMock, patch
from django.test import TestCase
@patch("hcaptcha.fields.hCaptchaField.validate", return_value=True)
class ContactTest(TestCase):
test_msg = {
"name": "pandora",
"message": "xyz",
"hcaptcha": "xxx", # Any truthy value is fine
}
def test_something(self, mock: MagicMock) -> None:
response = self.client.post("/contact/", self.test_msg)
self.assertEqual(response.status_code, HTTP_302_FOUND)
Metadata
Release files for django-hCaptcha 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-hCaptcha-0.2.0.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_hCaptcha-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.0 kB
Release files / django-hCaptcha-0.2.0.tar.gz
| Download URL | django-hCaptcha-0.2.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2519eaf0cc97865ac72f825301122c5cf61e1e4852d6895994160222acb6c1a
|
|
BLAKE2b-256 checksum How to use checksums |
84b160a4d048297ab0b1a692f27f35a45dec2b45ce79264b49c59f898c9c310b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.5
|
Release files / django_hCaptcha-0.2.0-py3-none-any.whl
| Download URL | django_hCaptcha-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
18804fb38a01827b6c65d111bac31265c1b96fcf52d7a54c3e2d2cb1c62ddcde
|
|
BLAKE2b-256 checksum How to use checksums |
d72f70ac35000d3bb6e69f12a9cd76c70d1ce3ed6ec86d70a76f5e0b5d49d0d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.5
|
Security for django-hCaptcha 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.