Fix the issue X-RateLimit-Limit, X-RateLimit-Remaining headers weren't able to be accessed by browsers #73
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
…rol-Expose-Headers configuration
kgmyatthu
changed the title
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.
Fix the issue X-RateLimit-Limit, X-RateLimit-Remaining headers weren't able to be accessed by browsers
This PR attempts to fix the issue we have with accessing X-RateLimit-Remaining headers in apod-api which described here #64
I think it is also critical that API consumer can monitor their API limits autonomously in applications. Since Expose Header is not set and thus almost every trusted modern browsers are preventing API consumers from accessing the X-RateLimit-Limit, X-RateLimit-Remaining headers.