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
I'm using Chrome Version 73.0.3683.86, and the accept header it makes for regular web pages is:
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3
With the new Accept header parsing in v3.10.0, the last entry is rejected with:
"application/signed-exchange;v=b3" is not a valid media type
Apologies for not catching that in review for PR #216.
I think to properly follow the production in RFC 7231, we should allow other parameters and only care if q is set.
q
The text was updated successfully, but these errors were encountered:
Just to clarify, installing django-health-check 3.10.0 and requesting the healthcheck page returns a 500:
Sorry, something went wrong.
Yes. #221 should fix that.
This is fixed in v3.10.1
ashokdelphia
No branches or pull requests
I'm using Chrome Version 73.0.3683.86, and the accept header it makes for regular web pages is:
With the new Accept header parsing in v3.10.0, the last entry is rejected with:
Apologies for not catching that in review for PR #216.
I think to properly follow the production in RFC 7231, we should allow other parameters and only care if
q
is set.The text was updated successfully, but these errors were encountered: