Update overview-authentication-authorization.md - headers example with a short explanation of their backend nature. #127185
+16
−0
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.
The article would be more helpful if it included a quick reference to the headers and a note about their server-side nature. This addition would save time, reduce confusion, and enhance the overall developer experience.
Documentation should answer the "what, where, and why" without requiring users to dig through multiple articles or community posts.
Knowing which headers are injected and what they contain is vital for developers.
Developers may assume they're missing something if they don't see the headers in browser DevTools. Explicitly stating that these headers are server-side only prevents unnecessary confusion.