Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Django 4.1.7 and 4.2 #1

Closed
ely-as opened this issue Apr 3, 2023 · 1 comment
Closed

Support Django 4.1.7 and 4.2 #1

ely-as opened this issue Apr 3, 2023 · 1 comment

Comments

@ely-as
Copy link
Owner

ely-as commented Apr 3, 2023

Django 4.2 introduces one new setting and deprecates two settings.

From Django 4.2 release notes | Django documentation | Django:

The new STORAGES setting allows configuring multiple custom file storage backends. It also controls storage engines for managing files (the "default" key) and static files (the "staticfiles" key).

The old DEFAULT_FILE_STORAGE and STATICFILES_STORAGE settings are deprecated as of this release.

@ely-as ely-as changed the title Support Django 4.2 Support Django 4.1.7 and 4.2 Apr 3, 2023
@ely-as
Copy link
Owner Author

ely-as commented Apr 3, 2023

Django 4.1.7 (and 3.2.18 and 4.0.10) also introduced one new setting.

From Django 4.1.7 release notes | Django documentation | Django:

Passing certain inputs to multipart forms could result in too many open files or memory exhaustion, and provided a potential vector for a denial-of-service attack.

The number of files parts parsed is now limited via the new DATA_UPLOAD_MAX_NUMBER_FILES setting.

ely-as added a commit that referenced this issue Apr 3, 2023
New settings:
- `DATA_UPLOAD_MAX_NUMBER_FILES` (4.1.7)
- `STORAGES` (4.2)
ely-as added a commit that referenced this issue Apr 3, 2023
@ely-as ely-as closed this as completed Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant