Return a more fun and cute animal picture to your users based upon the HTTP response codes.
Demo Responses
Some of these responses may look like:
404(Resource not found)
400(Bad request)
Installation
Install using pip.
$ python -m pip install django-cute-statusIf you want, you may install it from the source, grab the source code and run setup.py.
$ git clone git://github.com/abhiabhi94/django-cute-status.git
$ cd django-cute-status
$ python setup.py installUsage
Add app
To enable django_flag_app in your project you need to add it to INSTALLED_APPS in your projects settings.py file:
INSTALLED_APPS = (
...
'django_cute_status',
...
)Add middleware
Add the following middleware class to monitor the responses. Make sure it is at the bottom.
MIDDLEWARES = [
...
'django_cute_status.middleware.CuteStatusMiddleware',
]Configurations
There are certain configurations that allow you to customize the application.
CUTE_STATUS_BASE_URLS
This is the list of URLs to be used for displaying cute statuses. At the moment, the app only displays the pictures of dogs and cats. In case you know of any more such services(for e.g. one for pandas) you may add them here. Also, it would be great if you could take a moment to make a pull request to add the feature here as well. Defaults to :
= (
'https://http.dog/{status_code}.jpg',
'https://http.cat/{status_code}.jpg',
)CUTE_STATUS_BASE_URL
The default URL for displaying cute statuses. Suppose, you want only cat pictures as status code, you can use this by setting it to http://http.cat/{status_code}. This is useful only when you have set CUTE_STATUS_USE_RANDOM to False.
CUTE_STATUS_BASE_TEMPLATE
The base template used for rendering cute statuses. It is advisable to override this to cater the web page according to your needs. For example, you might want your header and footer etc. to also be added along the cute status codes. Defaults to 'django_cute_status/base.html'.
CUTE_STATUS_USE_RANDOM
This tells whether to display cute statuses using one of the available URLs randomly. Defaults to True.
CUTE_STATUS_FOR_CODES
This a list of status code for which cute status will be displayed. Defaults to cute_status_for_codes.
CUTE_STATUS_NOT_FOR_CODES
This is a list of status code for which cute status will not be displayed. You may want to display text as per you business logic. Defaults to cute_status_not_for_codes.
CUTE_STATUS_HEADER
This is the header sent added to the response. It can be useful in determining when you want to render your own responses, CSS, JS, media files etc. Defaults to 'X-Cute-Status'.
CUTE_STATUS_OVERRIDE_HEADER_ON_ALL
Whether to add the CUTE_STATUS_HEADER on all HTTP requests or not. Defaults to False.
Credits
The application wouldn’t have been possible without the excellent pictures served by https://http.dog and https://http.cat. Many thanks to them for their cute pictures.
Development
For setting up development environment, you may see the guidelines at CONTRIBUTING.rst.
1 maintainer
Metadata
1 maintainer
Release files for django-cute-status 2.0.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_cute_status-2.0.0.tar.gz | 5.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_cute_status-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.3 kB
Release files / django_cute_status-2.0.0.tar.gz
| Download URL | django_cute_status-2.0.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
786d96fccfc6a2bb4412cc61ae4d613ae6405d383d4f563b587f7bc48128e828
|
|
BLAKE2b-256 checksum How to use checksums |
22eebbcf021a14179c9cb391cb3e1c4a58545d6531049aff4780ed5db32a8684
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 25, 2025.
Transparency logRelease files / django_cute_status-2.0.0-py3-none-any.whl
| Download URL | django_cute_status-2.0.0-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c594a9607fc342f197e8755bd0575d2ac126426d3a8aeed8faeb5bf5300502b
|
|
BLAKE2b-256 checksum How to use checksums |
c8503e489f0c0ce255603924424d799dd880282624e81f04f6badde21bc97437
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 25, 2025.
Transparency logSecurity for django-cute-status 2.0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for django_cute_status-2.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 25, 2025.
Transparency logA 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.
