Skip to content
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

Remove redundant URL #90

Merged
merged 1 commit into from Jul 18, 2018
Merged

Remove redundant URL #90

merged 1 commit into from Jul 18, 2018

Conversation

dcreager
Copy link
Member

The Reporting API now lets us provide a custom URL to associate the report with. The default is to use the containing document's URL, which isn't relevant for a NEL report. This lets us remove the uri field from the NEL body, removing a source of confusion about why they're different.

The Reporting API now lets us provide a custom URL to associate the
report with.  The default is to use the containing document's URL,
which isn't relevant for a NEL report.  This lets us remove the `uri`
field from the NEL body, removing a source of confusion about why
they're different.
@dcreager
Copy link
Member Author

This depends on w3c/reporting#110

@dcreager dcreager merged commit f04c575 into w3c:gh-pages Jul 18, 2018
@dcreager dcreager deleted the no-uri branch July 18, 2018 13:27
aarongable pushed a commit to chromium/chromium that referenced this pull request Jul 19, 2018
Per w3c/network-error-logging#90, a NEL report's
`url` field now contains the (sanitized) URL of the request that the
report describes.  (Before that spec update, it was supposed to contain
the URL of the page that made the request, which isn't relevant for
NEL.)  Now that the report contains the "right" URL, the NEL body's
`uri` field is redundant, and can be removed.

Bug: 748549
Change-Id: Ibd2b0213b829e94329ecc7263baecd549d41e40c
Reviewed-on: https://chromium-review.googlesource.com/1141271
Reviewed-by: Misha Efimov <mef@chromium.org>
Commit-Queue: Douglas Creager <dcreager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#576312}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant