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

Check if djdt-store-id is in all headers before usage. #1651

Merged
merged 3 commits into from
Jul 12, 2022

Conversation

tim-schilling
Copy link
Member

Chromium throws an uncatchable warning when a header that
can't be accessed is used. While it's not problematic, it's
worrisome to developers. This avoids that by first checking
that it exists.

Fixes #1647

  • Change header to djdt-store-id.
  • Includes some tests to validate the HistoryPanel.get_headers
  • method.
  • Correct OBSERVE_REQUEST_CALLBACK default value in docs.

Chromium throws an uncatchable warning when a header that
can't be accessed is used. While it's not problematic, it's
worrisome to developers. This avoids that by first checking
that it exists.

Fixes #1647
Includes some tests to validate the HistoryPanel.get_headers
method.
@matthiask
Copy link
Member

LGTM, let's merge this despite the test failures (which are unrelated and have been happening for some time -- something changed re. selenium, I didn't take the time yet to investigate)

@matthiask matthiask merged commit a5ff45d into django-commons:main Jul 12, 2022
@tim-schilling tim-schilling deleted the auto-update-1647 branch October 13, 2022 13:40
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

Successfully merging this pull request may close these issues.

Refused to get unsafe header "djdt-store-id"
2 participants