Extends isProtectedRoute to allow HEAD requests #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
james-owen
approved these changes
Dec 14, 2019
jpope19
approved these changes
Dec 15, 2019
This commit is to address a problem that has been perplexing me for months. Whenever I try to make a HEAD request to a clay page I get a 302 redirect to `/_auth/login` instead of getting response headers from the page. The consequence of this behavior is that one is forced to render and download the full page contents, when they may only be interested in the Content-Length, status code, or other bits of information.
mattoberle
force-pushed
the
no-302s-on-head-requests
branch
from
f9abbea to
c178881
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit is to address a problem that has been perplexing me for months. Whenever I try to make a HEAD request to a clay page I get a 302 redirect to
/_auth/logininstead of getting response headers from the page.The consequence of this behavior is that one is forced to render and download the full page contents, when they may only be interested in the Content-Length, status code, or other bits of information.