Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
nghttp2
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
nghttp2
Commits
207d2d17
Commit
207d2d17
authored
Jul 22, 2013
by
Tatsuhiro Tsujikawa
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.rst
parent
42ff5b5c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
11 deletions
+14
-11
README.rst
README.rst
+14
-11
No files found.
README.rst
View file @
207d2d17
...
...
@@ -16,21 +16,24 @@ The following features are not implemented:
* Header continuation
* PRIORITY frame handling
* PUSH_PROMISE and server-push in general
* Client connection header: spdycat and spdyd do not send/handle
client connection header.
* ALPN: spdycat and spdyd use openssl without ALPN support and still
uses NPN to negotiate HTTP-draft-04/2.0.
* ALPN: ``nghttp`` client and ``nghttpd`` server use OpenSSL without ALPN
support and still use NPN to negotiate ``HTTP-draft-04/2.0``.
* HTTP Upgrade dance
With those missing parts, the library is not still inter-operable
right now.
The spdycat and spdyd are (the names are now odd for HTTP/2.0) working
now assuming the above limitation. You can see the HTTP/2.0 frames
back and forth and connection-level and stream level flow controls.
The ``nghttp`` client and ``nghttpd`` server are working now assuming
the above limitation. Both programs start HTTP/2.0 with `prior
knowledge
<http://tools.ietf.org/html/draft-ietf-httpbis-http2-04#section-3.4>`_
or TLS NPN negotiation. No HTTP upgrade dance is supported yet. You
can see the HTTP/2.0 frames back and forth and connection-level and
stream level flow controls.
Here is sample output from
spdyca
t::
Here is sample output from
``nghttp`` clien
t::
$ src/
spdycat
https://localhost:3000/COPYING http://localhost:3000/AUTHORS -nv --no-tls
$ src/
nghttp
https://localhost:3000/COPYING http://localhost:3000/AUTHORS -nv --no-tls
[ 0.000] Handshake complete
[ 0.000] recv SETTINGS frame <length=8, flags=0, stream_id=0>
(niv=1)
...
...
@@ -63,7 +66,7 @@ Here is sample output from spdycat::
content-length: 1080
date: Fri, 19 Jul 2013 17:02:21 GMT
last-modified: Fri, 12 Jul 2013 14:55:22 GMT
server:
spdy
d nghttp2/0.1.0-DEV
server:
nghttp
d nghttp2/0.1.0-DEV
[ 0.001] recv DATA frame (length=1080, flags=0, stream_id=1)
[ 0.001] recv DATA frame (length=0, flags=1, stream_id=1)
[ 0.001] recv HEADERS frame <length=6, flags=4, stream_id=3>
...
...
@@ -74,7 +77,7 @@ Here is sample output from spdycat::
content-length: 66
date: Fri, 19 Jul 2013 17:02:21 GMT
last-modified: Fri, 12 Jul 2013 14:55:22 GMT
server:
spdy
d nghttp2/0.1.0-DEV
server:
nghttp
d nghttp2/0.1.0-DEV
[ 0.001] recv DATA frame (length=66, flags=0, stream_id=3)
[ 0.001] recv DATA frame (length=0, flags=1, stream_id=3)
[ 0.001] send GOAWAY frame <length=8, flags=0, stream_id=0>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment