Confirmed users
72
edits
Networking/Archive/http2: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
The current implementation is of draft-06 and compression-03. | The current implementation is of draft-06 and compression-03. | ||
It is serial | It is serial 021 cset 613c073aaeab on try | ||
This build uses 0-bit prefix encodings for name and value lengths in the compression block. The specification is unclear on whether those should be 8 bit prefixes or 0 bit prefixes. twitter.com uses 0-bit as well, akamai and katana have favored 8, iij has transitioned from 0 to 8. Future compression definitions will define this more clearly (presumably as 8, which is more efficient) and will provide better interop. | This build uses 0-bit prefix encodings for name and value lengths in the compression block. The specification is unclear on whether those should be 8 bit prefixes or 0 bit prefixes. twitter.com uses 0-bit as well, akamai and katana have favored 8, iij has transitioned from 0 to 8. Future compression definitions will define this more clearly (presumably as 8, which is more efficient) and will provide better interop. | ||
source is at | source is at | ||
https://tbpl.mozilla.org/?tree=Try&rev= | https://tbpl.mozilla.org/?tree=Try&rev=613c073aaeab | ||
Builds for windows, os x, and linux are at | Builds for windows, os x, and linux are at | ||
https://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/mcmanus@ducksong.com- | https://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/mcmanus@ducksong.com-613c073aaeab/ | ||
Firefox will only be implementing HTTP/2 over TLS - and right now that means for https:// schemed URLs. It does enforce the protocol's >= TLS 1.1 requirement - if a server negotiates HTTP/2 with a lower TLS version it is treated as a protocol error. (there is a preference for changing that for testing purposes if you need it.) | Firefox will only be implementing HTTP/2 over TLS - and right now that means for https:// schemed URLs. It does enforce the protocol's >= TLS 1.1 requirement - if a server negotiates HTTP/2 with a lower TLS version it is treated as a protocol error. (there is a preference for changing that for testing purposes if you need it.) | ||