Closed
Bug 1362522
Opened 8 years ago
Closed 8 years ago
Investigate why a bunch of requests disallow spdy
Categories
(Core :: Networking, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: u408661, Assigned: u408661)
Details
(Whiteboard: [necko-next])
Digging through my http logs for a bug I'm working on today (which involves explicitly disallowing spdy on certain connections) has made me notice that we disallow spdy on a *lot* of our automagic connections (safebrowsing, telemetry, addons are just a few of the ones I've seen). We should figure out *why* these are the way they are, potentially document them if they need to stay that way (so someone, possibly even me, doesn't go through this again in the future), and change them to use spdy if we think that's a good idea.
I will note explicitly that these other connections that disallow spdy are *not* because of a bug in my patch (I've already tested against latest nightly to make sure).
Ugh, I was misreading the logs here. I saw "401" as the caps and assumed it was being reported as a %d (which would mean bit 7, disable spdy, was set). It was actually being reported as %x, so bit 7 is unset and these were running h2 just fine (which I also verified by looking later in the logs and seeing those transactions being dispatched over h2 connections).
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•