Closed
Bug 1248049
Opened 9 years ago
Closed 9 years ago
Don't HTTP cache XHR POSTs
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla47
People
(Reporter: mayhemer, Assigned: mayhemer)
References
Details
(Keywords: regression)
Attachments
(1 file, 2 obsolete files)
2.82 KB,
patch
|
jdm
:
review+
Sylvestre
:
approval-mozilla-aurora+
Sylvestre
:
approval-mozilla-beta+
Sylvestre
:
approval-mozilla-release-
|
Details | Diff | Splinter Review |
AFAIK we cache POSTs only to allow back/forth caching and resend. Nothing more. XHR POST response will never be reused from cache, I think.
Can we set INHIBIT_CACHING to spare memory, disk spin and CPU?
Could somewhat help with bug 1215970.
Flags: needinfo?(bzbarsky)
![]() |
Assignee | |
Comment 1•9 years ago
|
||
Note that POST response cannot be reused unless nsICacheInfoChannel.cacheKey is explicitly set to the proper internal unique POST id. Only doc shell and nsWebBrowserPersist do that.
![]() |
||
Comment 2•9 years ago
|
||
I was going to say "we already do that". But it looks like the code I remembered us having got removed in bug 1176988, which totally should have gotten review from a necko peer. :(
Do we just want to reinstate that codepath with the INHIBIT_CACHING flag (but without the LOAD_BYPASS_CACHE flag, I guess)?
Flags: needinfo?(bzbarsky)
![]() |
||
Comment 3•9 years ago
|
||
Anyway, this is clearly a new regression in 43... :(
Blocks: 1176988
Keywords: regression
![]() |
Assignee | |
Updated•9 years ago
|
status-firefox44:
--- → affected
status-firefox45:
--- → affected
status-firefox46:
--- → affected
status-firefox-esr45:
--- → affected
![]() |
Assignee | |
Comment 4•9 years ago
|
||
Should not be a problem to pass also LOAD_BYPASS_CACHE since in case of possible interception we still open a cache entry from synthetic storage (open truncate).
https://treeherder.mozilla.org/#/jobs?repo=try&revision=ee1b8b5b1464
![]() |
Assignee | |
Comment 5•9 years ago
|
||
The test failure
TEST-UNEXPECTED-FAIL | /XMLHttpRequest/setrequestheader-header-allowed.htm | XMLHttpRequest: setRequestHeader() - headers that are allowed (Pragma) - assert_equals: expected "pragma," but got ""
expectancy has been removed with bug 1176988. As this is actually a partial backout of that bug, this has to be readded as well.
Otherwise, the patch doesn't cause any failures!
https://treeherder.mozilla.org/#/jobs?repo=try&revision=667bc0782388
Attachment #8719035 -
Attachment is obsolete: true
Attachment #8719035 -
Flags: review?(josh)
Attachment #8719456 -
Flags: review?(josh)
![]() |
Assignee | |
Comment 6•9 years ago
|
||
Better try run (w/o bug 1247644, that is not strictly necessary to fix SCtC problem):
https://treeherder.mozilla.org/#/jobs?repo=try&revision=07dc7aa24bad
![]() |
||
Comment 7•9 years ago
|
||
> As this is actually a partial backout of that bug, this has to be readded as well.
Well, hold on. That means we're adding an explicit spec violation that we had removed. Can we please avoid doing that? A followup is probably OK, as long as we actually fix things....
![]() |
Assignee | |
Comment 8•9 years ago
|
||
OK, followup is necessary because we need to quickly fix a top crash/high jank bug.
![]() |
Assignee | |
Comment 9•9 years ago
|
||
(In reply to Boris Zbarsky [:bz] from comment #7)
> > As this is actually a partial backout of that bug, this has to be readded as well.
>
> Well, hold on. That means we're adding an explicit spec violation that we
> had removed. Can we please avoid doing that? A followup is probably OK, as
> long as we actually fix things....
Filed bug 1248613.
![]() |
Assignee | |
Comment 10•9 years ago
|
||
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1248613#c4
using LOAD_BYPASS_LOCAL_CACHE that does the job we want and doesn't reintroduce the regression.
Attachment #8719456 -
Attachment is obsolete: true
Attachment #8719456 -
Flags: review?(josh)
Attachment #8719841 -
Flags: review?(josh)
![]() |
Assignee | |
Comment 11•9 years ago
|
||
Updated•9 years ago
|
Attachment #8719841 -
Flags: review?(josh) → review+
Comment 13•9 years ago
|
||
Keywords: checkin-needed
![]() |
Assignee | |
Comment 14•9 years ago
|
||
Comment on attachment 8719841 [details] [diff] [review]
v2
[Approval Request Comment]
Bug caused by (feature/regressing bug #): bug 1176988
User impact if declined: major slowdown in overall responsiveness, shutdown hanging when using certain combination of favorite addons (Skype Click to Call) and various favorite A/V software, see bug 1215970 comment 98 and 100
Testing completed: try runs, local testing, just landed
Risk to taking this patch (and alternatives if risky): I believe very very low, we had similar (not identical tho!) behavior before bug 1176988 (i.e. in Fx42)
String or UUID changes made by this patch: none
Attachment #8719841 -
Flags: approval‑mozilla‑b2g44?
Attachment #8719841 -
Flags: approval-mozilla-release?
Attachment #8719841 -
Flags: approval-mozilla-beta?
Attachment #8719841 -
Flags: approval-mozilla-aurora?
Comment 15•9 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla47
Updated•9 years ago
|
Comment 17•9 years ago
|
||
Comment on attachment 8719841 [details] [diff] [review]
v2
Hopefully fix the famous Skype crash... Taking it.
Should be in 45 beta 7
Attachment #8719841 -
Flags: approval-mozilla-beta?
Attachment #8719841 -
Flags: approval-mozilla-beta+
Attachment #8719841 -
Flags: approval-mozilla-aurora?
Attachment #8719841 -
Flags: approval-mozilla-aurora+
Comment 18•9 years ago
|
||
bugherder uplift |
Comment 19•9 years ago
|
||
bugherder uplift |
Updated•9 years ago
|
Comment 20•9 years ago
|
||
Comment on attachment 8719841 [details] [diff] [review]
v2
No longer relevant
Attachment #8719841 -
Flags: approval-mozilla-release? → approval-mozilla-release-
![]() |
Assignee | |
Comment 21•9 years ago
|
||
Comment on attachment 8719841 [details] [diff] [review]
v2
Apparently, no one wants this patch on that old B2G.
Attachment #8719841 -
Flags: approval‑mozilla‑b2g44?
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•