Why did Firefox respond with REFUSED_STREAM for an HTTP2 server push?
I have a site that pushes a few resources back with the initial page load via HTTP2 server push. This site worked well in Firefox 72, and still works well with Chrome 80. It does not work in Firefox 74. Charles proxy reports that Firefox is resetting the push stream via REFUSED_STREAM (0x7).
Before I take the time to setup a publicly accessible repro: 1. Has anyone else seen this? 2. Are there other debugging tools folks recommend? I'd like to rule out some of the many legitimate reasons (https://jakearchibald.com/2017/h2-push-tougher-than-i-thought/) the stream could have been refused before reporting this as a bug.
All Replies (3)
Hi adam43, I'm not familiar with this. Does anything in the developer-oriented release notes relate to this change?
If you didn't test in Firefox 73, you might check those release notes as well.
This is a user oriented support forum. For developer support please post a question on stackoverflow and tag it firefox:
You can remove all data stored in Firefox for a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History -> Show All History" or "View -> Sidebar -> History").
Using "Forget About This Site" will remove all data stored in Firefox for this domain like history and cookies and passwords and exceptions and cache, so be cautious. If you have a password or other data for that domain that you do not want to lose then make sure to backup this data or make a note.
You can't recover from this 'forget' unless you have a backup of involved files.
If you revisit a 'forgotten' website then data for that website will be saved once again.