Closed
Bug 1077714
Opened 10 years ago
Closed 8 years ago
Blocked resources shown as successful network requests in Network Inspector
Categories
(DevTools :: Netmonitor, defect)
DevTools
Netmonitor
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mwobensmith, Unassigned)
Details
Attachments
(3 files)
1. Edit these two prefs: browser.safebrowsing.debug privacy.trackingprotection.enabled 2. Clear cache. 3. Visit youtube.com and observe traffic in Network Inspector. Result: Some resources on the page are blocked, as expected, but inspector indicates successful HTTP responses for all page resources. Expected: Blocked resources (as above) but those that are blocked should not have HTTP success codes displayed next to them.
Reporter | ||
Comment 1•10 years ago
|
||
Bug is probably in the wrong component, but wasn't sure - feel free to recategorize.
Blocks: 1029886
Comment 2•10 years ago
|
||
Matt, I may have to end up just building you a custom addon that lists blocked elements instead. Would that work?
Comment 3•10 years ago
|
||
We may also be incorrectly caching classification responses.
Comment 4•10 years ago
|
||
This is maybe a clearer test case. This test page loads the same resource as 4 times, once as a script, twice as an iframe and once as an image. The resource never loads and the first 2 loads show correctly as grey, but the second 2 show as green though the channel is cancelled. snorp, is this a known issue? <html> <head> <!-- bad script url --> <script id="testscript" type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js?js"></script> </head> <body> <p>Hello World</p> <!-- bad iframe url --> <iframe id="testiframe" src="http://pagead2.googlesyndication.com/pagead/show_ads.js?iframe"></iframe> <iframe id="testiframe" src="http://pagead2.googlesyndication.com/pagead/show_ads.js?iframe"></iframe> <!--<iframe src="http://www.example.com"></iframe>--> <!-- bad image url --> <img id="testimage" src="http://pagead2.googlesyndication.com/pagead/show_ads.js?img"></img> <iframe src="http://doubleclick.net/"></iframe> </body> </html>
Flags: needinfo?(snorp)
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to [:mmc] Monica Chew (please use needinfo) from comment #2) > Matt, I may have to end up just building you a custom addon that lists > blocked elements instead. Would that work? Whatever you like. At your command. :)
Comment 6•10 years ago
|
||
Removing the dependency since https://bugzilla.mozilla.org/show_bug.cgi?id=1079338 landed.
No longer blocks: 1029886
Comment 7•10 years ago
|
||
(In reply to [:mmc] Monica Chew (please use needinfo) from comment #4) Oh, I have no idea. Let's ask a networking person!
Flags: needinfo?(mcmanus)
Comment 8•10 years ago
|
||
so the channel receives both onstartrequest and onstoprequest with status = NS_ERROR_TRACKING_URI there are no response headers for any of the transactions.. but the last two show in dev tools as 200 OK.. I guess I would need to ask the devtools folks where that comes from. I bet its some kind of a default in necko and devtools is ignoring the error on the channel.
Flags: needinfo?(mcmanus)
Updated•10 years ago
|
Flags: needinfo?(snorp)
Updated•8 years ago
|
Component: DOM: Security → Developer Tools: Netmonitor
Product: Core → Firefox
Comment 9•8 years ago
|
||
Brian, any chance you can take a look or assign it to the right people?
Flags: needinfo?(bgrinstead)
Comment 10•8 years ago
|
||
Test case that includes an iframe and image pointing to http://trackertest.org
Comment 11•8 years ago
|
||
Is this still a bug? I can't reproduce it - I don't see any requests in the netmonitor for the blocked requests but I do get a notification in the console that they are blocked.
Flags: needinfo?(bgrinstead) → needinfo?(mozilla)
Comment 12•8 years ago
|
||
(In reply to Brian Grinstead [:bgrins] from comment #11) > Created attachment 8727957 [details] > blocked-requests.png > > Is this still a bug? I can't reproduce it - I don't see any requests in the > netmonitor for the blocked requests but I do get a notification in the > console that they are blocked. Thanks Brian. That Bug was openend in late 2014. I already thought that some changeset fixed the problem in the meantime. Thanks for verifying - let's close this bug as WORKSFORME.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(mozilla)
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•