MicrosoftDocs
Update overview-authentication-authorization.md - headers example with a short explanation of their backend nature.
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.
@theluckyprogrammer : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit c70845b:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/app-service/overview-authentication-authorization.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@cephalin - Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@cephalin Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?
Thanks!
@cephalin
Can you review this old PR and determine whether it needs to be closed or merged?
@MicrosoftDocs/public-repo-pr-review-team
I sent email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
I sent a Teams message to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
The info is duplicate of what's in https://learn.microsoft.com/en-us/azure/app-service/configure-authentication-user-identities#access-user-claims-in-app-code.
#please-close
