doc: add note about browsers and HTTP/2#19476
Conversation
|
/cc @apapirovski @a0viedo @mcollina @trivikr I'm not sure the best way to word this or how to make it more explicit. |
doc/api/http2.md
Outdated
There was a problem hiding this comment.
A nit: // Try -> // try after the comma above?
There was a problem hiding this comment.
Any thoughts on usage of periods . anywhere?
There was a problem hiding this comment.
Let's see what others think, I am not a native speaker)
doc/api/http2.md
Outdated
There was a problem hiding this comment.
No browsers support unencrypted HTTP2 (HTTP/2 spec FAQ)
You can change this to "since no browsers support unencrypted HTTP2" with the link to HTTP/2 spec FAQ
Ditto for line 1735
doc/api/http2.md
Outdated
There was a problem hiding this comment.
I think the term plain-text is more specific.
There was a problem hiding this comment.
How about using the term unencrypted over plain-text?
doc/api/http2.md
Outdated
There was a problem hiding this comment.
can you restore this to plain-text?
|
Thanks for the comments. I pushed an update with the revised docs. |
doc/api/http2.md
Outdated
There was a problem hiding this comment.
A nit: we usually sort references in ASCII order, so this should go after [HTTP2 Settings Object] ref.
There was a problem hiding this comment.
I fixed this by renaming to [HTTP/2 Unencrypted] since its not linking to a section anchor but its more like the external link above.
doc/api/http2.md
Outdated
There was a problem hiding this comment.
A nit: missing line break at the end of the file.
| The following illustrates a simple HTTP/2 server using the Core API. | ||
| Since no browsers support [unencrypted HTTP/2][HTTP/2 Unencrypted], | ||
| the use of [`http2.createSecureServer()`][] is preferred. | ||
|
|
There was a problem hiding this comment.
I would say something like...
Since there are no browsers known that support [unencrypted HTTP/2](HTTP/2 Unencrypted),
the use of [`http2.createSecureServer()`][] is necessary when communicating with browser
clients.
Using Unencrypted HTTP/2 would actually be the preference when running purely within internal environments with non-browser clients.
doc/api/http2.md
Outdated
There was a problem hiding this comment.
Again,
Since there are no browsers known that support [unencrypted HTTP/2](HTTP/2 Unencrypted),
the use of [`http2.createSecureServer()`][] is necessary when communicating with browser
clients.
doc/api/http2.md
Outdated
There was a problem hiding this comment.
(HTTP/2 Unencrypted)->[HTTP/2 Unencrypted](otherwise it is not rendered as a link).- This and next line exceed 80 character length, so this may be a problem for doc linting
There was a problem hiding this comment.
Whoa good catch, I just copy/pasted the code review comment so there must have been a typo.
doc/api/http2.md
Outdated
|
Thanks for all the feedback! I think I got it right this time 🤞 |
trivikr
left a comment
There was a problem hiding this comment.
Confirmed the doc edits are appearing correctly at https://github.com/styfle/node/blob/patch-2/doc/api/http2.md
PR-URL: #19476 Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Landed in cb69a7d Thank you for the patience! |
PR-URL: #19476 Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#19476 Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
The docs were not clear for new users of HTTP/2 requires TLS in most browsers.
This adds a couple notes to direct new users to
http2.createSecureServer().Fixes #19406
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
doc