-
Notifications
You must be signed in to change notification settings - Fork 1.3k
adjust RUM response status documentation #28270
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
Conversation
It turns out Browsers are enforcing different rules to access response status.
drichards-87
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few minor suggestions. Also, just an FYI that there's a merge conflict in the PR.
content/en/real_user_monitoring/browser/monitoring_resource_performance.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/browser/monitoring_resource_performance.md
Outdated
Show resolved
Hide resolved
content/en/real_user_monitoring/browser/monitoring_resource_performance.md
Outdated
Show resolved
Hide resolved
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
|
Thank you @drichards-87 , I commited your suggestions and fixed the conflicts! |
Preview links (active after the
|
drichards-87
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do? What is the motivation?
It turns out Browsers are enforcing different rules to access response status. For detailed timings,
Timing-Allow-Originis needed, but for status code,Access-Control-Allow-Originheaders and thecrossoriginattribute are needed.Merge instructions
Merge readiness:
Merge queue is enabled in this repo. Your branch name MUST follow the
<slack_username>/<branch_name>convention, or your pull request will not pass in CI. If your branch doesn't follow this format, rename it or create a new branch and PR.To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes