doc: fix some links in http2.md
PR-URL: https://github.com/nodejs/node/pull/15481 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Bryan English <bryan@bryanenglish.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This commit is contained in:
parent
ee46c73023
commit
6763fb2f0e
@ -16,7 +16,8 @@ in order to use the `'http2'` module.
|
|||||||
|
|
||||||
The Core API provides a low-level interface designed specifically around
|
The Core API provides a low-level interface designed specifically around
|
||||||
support for HTTP/2 protocol features. It is specifically *not* designed for
|
support for HTTP/2 protocol features. It is specifically *not* designed for
|
||||||
compatibility with the existing [HTTP/1][] module API. However, the [Compatibility API][] is.
|
compatibility with the existing [HTTP/1][] module API. However,
|
||||||
|
the [Compatibility API][] is.
|
||||||
|
|
||||||
The following illustrates a simple, plain-text HTTP/2 server using the
|
The following illustrates a simple, plain-text HTTP/2 server using the
|
||||||
Core API:
|
Core API:
|
||||||
@ -1305,7 +1306,7 @@ added: v8.4.0
|
|||||||
* `response` {http2.Http2ServerResponse}
|
* `response` {http2.Http2ServerResponse}
|
||||||
|
|
||||||
Emitted each time there is a request. Note that there may be multiple requests
|
Emitted each time there is a request. Note that there may be multiple requests
|
||||||
per session. See the [Compatibility API](compatiblity-api).
|
per session. See the [Compatibility API][].
|
||||||
|
|
||||||
#### Event: 'timeout'
|
#### Event: 'timeout'
|
||||||
<!-- YAML
|
<!-- YAML
|
||||||
@ -1413,7 +1414,7 @@ added: v8.4.0
|
|||||||
* `response` {http2.Http2ServerResponse}
|
* `response` {http2.Http2ServerResponse}
|
||||||
|
|
||||||
Emitted each time there is a request. Note that there may be multiple requests
|
Emitted each time there is a request. Note that there may be multiple requests
|
||||||
per session. See the [Compatibility API](compatiblity-api).
|
per session. See the [Compatibility API][].
|
||||||
|
|
||||||
#### Event: 'timeout'
|
#### Event: 'timeout'
|
||||||
<!-- YAML
|
<!-- YAML
|
||||||
@ -1915,8 +1916,8 @@ req.end('Jane');
|
|||||||
|
|
||||||
The Compatibility API has the goal of providing a similar developer experience
|
The Compatibility API has the goal of providing a similar developer experience
|
||||||
of HTTP/1 when using HTTP/2, making it possible to develop applications
|
of HTTP/1 when using HTTP/2, making it possible to develop applications
|
||||||
that supports both [HTTP/1](HTTP/1) and HTTP/2. This API targets only the
|
that supports both [HTTP/1][] and HTTP/2. This API targets only the
|
||||||
**public API** of the [HTTP/1](HTTP/1), however many modules uses internal
|
**public API** of the [HTTP/1][], however many modules uses internal
|
||||||
methods or state, and those _are not supported_ as it is a completely
|
methods or state, and those _are not supported_ as it is a completely
|
||||||
different implementation.
|
different implementation.
|
||||||
|
|
||||||
@ -1976,7 +1977,7 @@ function onRequest(req, res) {
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
The `'request'` event works identically on both [HTTPS](https) and
|
The `'request'` event works identically on both [HTTPS][] and
|
||||||
HTTP/2.
|
HTTP/2.
|
||||||
|
|
||||||
### Class: http2.Http2ServerRequest
|
### Class: http2.Http2ServerRequest
|
||||||
@ -2605,7 +2606,7 @@ added: v8.4.0
|
|||||||
Sends a response header to the request. The status code is a 3-digit HTTP
|
Sends a response header to the request. The status code is a 3-digit HTTP
|
||||||
status code, like `404`. The last argument, `headers`, are the response headers.
|
status code, like `404`. The last argument, `headers`, are the response headers.
|
||||||
|
|
||||||
For compatibility with [HTTP/1](), a human-readable `statusMessage` may be
|
For compatibility with [HTTP/1][], a human-readable `statusMessage` may be
|
||||||
passed as the second argument. However, because the `statusMessage` has no
|
passed as the second argument. However, because the `statusMessage` has no
|
||||||
meaning within HTTP/2, the argument will have no effect and a process warning
|
meaning within HTTP/2, the argument will have no effect and a process warning
|
||||||
will be emitted.
|
will be emitted.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user