16👍
✅
Django has a build in mechanism to prevent any suspicious activity.
In your settings.py file set the variable
DATA_UPLOAD_MAX_MEMORY_SIZE = 10*1024*1024 # your size limit in bytes
See documentation: https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-DATA_UPLOAD_MAX_MEMORY_SIZE
4👍
If your team was/is using Django Channels, there was a piece of code introduced in 2.1.7
causing an unintended 413 error (discussed here). This was fixed in 2.3.0
, however.
- Django WeasyPrint CSS integration warning: Relative URI reference without a base URI: <link href="/static/css/bootstrap.min.css"> at line None
- How to connect PyCharm to a Heroku postgres database
1👍
As far as I know runserver or daphne will never return a 413. Looks like you have NGINX in front of the python server.
You can change the limit with client_max_body_size in the server block in nginx.conf
server {
client_max_body_size 20M;
listen 80;
server_name localhost;
location / {
proxy_pass http://127.0.0.1:8000/;
}
}
- Django no module named "compressor"
- Django 1.8: Migrations not detected after deleting migrations folder
Source:stackexchange.com