Closed
Bug 1980239
Opened 10 months ago
Closed 10 months ago
moz-cached-ohttp channel should set contentType on itself when pulling resources from the cache
Categories
(Firefox :: New Tab Page, task)
Firefox
New Tab Page
Tracking
()
RESOLVED
FIXED
143 Branch
| Tracking | Status | |
|---|---|---|
| firefox143 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
Details
Attachments
(1 file)
At load time, when getting (for example, an SVG image) over OHTTP, we correctly set the contentType on the channel by reading the content type header from the nsIObliviousHttpChannel.
When, however, we pull the image from the cache, we do no such thing. The existing implementation has not been caching the content type (which it should), and when we pull from the cache, we should update the content type on the channel to match it.
| Assignee | ||
Comment 1•10 months ago
|
||
Updated•10 months ago
|
Assignee: nobody → mconley
Status: NEW → ASSIGNED
Pushed by mconley@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/3c8ab5f89cbe
https://hg.mozilla.org/integration/autoland/rev/cd17d932f90c
Include the content type when storing / retrieving cache entries via moz-cached-ohttp. r=kershaw
Comment 3•10 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
status-firefox143:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch
Updated•9 months ago
|
QA Whiteboard: [qa-triage-done-c144/b143]
You need to log in
before you can comment on or make changes to this bug.
Description
•