Closed Bug 1307190 Opened 3 years ago Closed 3 years ago

Unable to connect to ksd.org with non-default HPACK table size

Categories

(Web Compatibility :: Desktop, defect, major)

Firefox 52
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u408661, Assigned: u408661)

References

Details

(Whiteboard: [sitewait])

See bug 1306481 comment 10 - this looks like a server-side bug in apache (similar to bug 1305321), but I want to investigate a bit more to be sure before sending this over to tech evang.
I'm unable to reproduce this with latest apache httpd (2.4.23) + mod_http2 locally. Testing with nghttp2 with SETTINGS_HEADER_TABLE_SIZE=65536, ksd.org behaves the same as it does with firefox (sends a GOAWAY/PROTOCOL_ERROR without processing any requests). I'm calling this an evangelism bug - they need to upgrade their httpd, as their current version obviously has a bug.
Component: Networking: HTTP → Desktop
Product: Core → Tech Evangelism
Version: 51 Branch → Firefox 52
Behavior is also the same with chrome canary (which has the same change as Firefox) - no connection or data downloaded from ksd.org
I just sent an email to the web developer for ksd.org with an link to this bug and details on the issue.
Whiteboard: [necko-active] → [necko-active][sitewait]
Whiteboard: [necko-active][sitewait] → [sitewait]
The problem has been fixed on our end.

For what it's worth, the service you were connecting to is actually running nodejs with the 'spdy' module for http2. spdy 3.3.x has the bug, spdy 3.4.x does not, and we've been running 3.4.x in production on other servers. Bumped this to 3.4.3 and tested it out and the site came up without issue.

Thanks for the information - this probably would have persisted for a while until new versions of Firefox and Chrome that actually triggered the issue were released and I would have been pulling my hair out trying to figure out what happened.
Awesome, thanks for the quick turnaround, Chris! I can confirm using the latest Firefox nightly, Chrome canary, and nghttp2 that this is fixed.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.