Open Quuxplusone opened 6 years ago
Quuxplusone
commented
6 years ago | Bugzilla Link | PR35888 |
| Status | NEW |
| Importance | P normal |
| Reported by | Lorenzo Tilve (ltilve@igalia.com) |
| Reported on | 2018-01-10 08:55:38 -0800 |
| Last modified on | 2018-02-06 08:15:32 -0800 |
| Version | 5.0 |
| Hardware | PC Linux |
| CC | dgregor@apple.com, llvm-bugs@lists.llvm.org |
| Fixed by commit(s) | |
| Attachments | |
| Blocks | |
| Blocked by | |
| See also |
Quuxplusone
commented
6 years ago That trace was produced on a build that failed with clang-4.0, but a similar error happens with clang-5.0.
Quuxplusone
commented
6 years ago The issue is still present when building Chromium 64 on the same part of the
code, which is processing the following annotation:
const net::NetworkTrafficAnnotationTag kNavigationUrlLoaderTrafficAnnotation =
net::DefineNetworkTrafficAnnotation("navigation_url_loader", R"(
semantics {
sender: "Navigation URL Loader"
description:
"This request is issued by a main frame navigation to fetch the "
"content of the page that is being navigated to."
trigger:
"Navigating Chrome (by clicking on a link, bookmark, history item, "
"using session restore, etc)."
data:
"Arbitrary site-controlled data can be included in the URL, HTTP "
"headers, and request body. Requests may include cookies and "
"site-specific credentials."
destination: WEBSITE
}
policy {
cookies_allowed: YES
cookies_store: "user"
setting: "This feature cannot be disabled."
chrome_policy {
URLBlacklist {
URLBlacklist: { entries: '*' }
}
}
chrome_policy {
URLWhitelist {
URLWhitelist { }
}
}
}
comments:
"Chrome would be unable to navigate to websites without this type of "
"request. Using either URLBlacklist or URLWhitelist policies (or a "
"combination of both) limits the scope of these requests."
)");
https://chromium.googlesource.com/chromium/src.git/+/64.0.3282.119/content/browser/loader/navigation_url_loader_network_service.cc#81