We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
parse_header
parse_header_parameters
Originally posted by Scotchester June 29, 2022 Hi folks,
The Wagtail project has a check against Django's main branch in our CI, and it started failing a day or two ago due to the removal of django.http.multipartparser.parse_header(), which DRF uses in three places. This change will be released in Django 4.2.
main
django.http.multipartparser.parse_header()
The recommended solution is to switch to django.utils.http.parse_header_parameters().
django.utils.http.parse_header_parameters()
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Discussed in #8539
Originally posted by Scotchester June 29, 2022
Hi folks,
The Wagtail project has a check against Django's
main
branch in our CI, and it started failing a day or two ago due to the removal ofdjango.http.multipartparser.parse_header()
, which DRF uses in three places. This change will be released in Django 4.2.The recommended solution is to switch to
django.utils.http.parse_header_parameters()
.The text was updated successfully, but these errors were encountered: