Closed
Bug 1012873
Opened 10 years ago
Closed 8 years ago
Cache negative responses for sourcemaps on the client
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hsteen, Unassigned)
References
(Blocks 1 open bug, )
Details
Often while debugging, I see Firefox hammering servers requesting missing .map files if the developer tools are open.
For example, today I was looking at mapquest.com mobile site. It includes http://content.mqcdn.com/mobileweb-advanced-804/media/js/mqm-site.js which contains //@ sourceMappingURL=jquery.min.map - and I've logged 490 requests for http://content.mqcdn.com/mobileweb-advanced-804/media/js/jquery.min.map . (Response is mostly 404, sometimes 504 gateway timeout error).
Firefox fires off something like 30 requests at a time. The implementation should be reviewed to see why there are so many simultaneous requests, and we should cache negative responses for some period of time. Bonus points if the cache can be annotated with a hash of the file referencing it or something, so that if the file's content changes the cache is invalidated..
Comment 2•10 years ago
|
||
> we should cache negative responses for some period of time.
Ideally it would be cached per navigation.
Updated•10 years ago
|
Blocks: dbg-sourcemap
Updated•10 years ago
|
Summary: cache negative source map responses for the duration of the session (or something like that..) → Cache negative responses for sourcemaps on the client
Updated•8 years ago
|
Priority: -- → P3
Comment 3•8 years ago
|
||
the new UI caches source map requests.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•