@@ -16,7 +16,8 @@ in order to use the `'http2'` module.
16
16
17
17
The Core API provides a low-level interface designed specifically around
18
18
support for HTTP/2 protocol features. It is specifically * not* designed for
19
- compatibility with the existing [ HTTP/1] [ ] module API. However, the [ Compatibility API] [ ] is.
19
+ compatibility with the existing [ HTTP/1] [ ] module API. However,
20
+ the [ Compatibility API] [ ] is.
20
21
21
22
The following illustrates a simple, plain-text HTTP/2 server using the
22
23
Core API:
@@ -1305,7 +1306,7 @@ added: v8.4.0
1305
1306
* ` response ` {http2.Http2ServerResponse}
1306
1307
1307
1308
Emitted each time there is a request. Note that there may be multiple requests
1308
- per session. See the [ Compatibility API] ( compatiblity-api ) .
1309
+ per session. See the [ Compatibility API] [ ] .
1309
1310
1310
1311
#### Event: 'timeout'
1311
1312
<!-- YAML
@@ -1413,7 +1414,7 @@ added: v8.4.0
1413
1414
* ` response ` {http2.Http2ServerResponse}
1414
1415
1415
1416
Emitted each time there is a request. Note that there may be multiple requests
1416
- per session. See the [ Compatibility API] ( compatiblity-api ) .
1417
+ per session. See the [ Compatibility API] [ ] .
1417
1418
1418
1419
#### Event: 'timeout'
1419
1420
<!-- YAML
@@ -1915,8 +1916,8 @@ req.end('Jane');
1915
1916
1916
1917
The Compatibility API has the goal of providing a similar developer experience
1917
1918
of HTTP/1 when using HTTP/2, making it possible to develop applications
1918
- that supports both [ HTTP/1] ( HTTP/1 ) and HTTP/2. This API targets only the
1919
- ** public API** of the [ HTTP/1] ( HTTP/1 ) , however many modules uses internal
1919
+ that supports both [ HTTP/1] [ ] and HTTP/2. This API targets only the
1920
+ ** public API** of the [ HTTP/1] [ ] , however many modules uses internal
1920
1921
methods or state, and those _ are not supported_ as it is a completely
1921
1922
different implementation.
1922
1923
@@ -1976,7 +1977,7 @@ function onRequest(req, res) {
1976
1977
}
1977
1978
```
1978
1979
1979
- The ` 'request' ` event works identically on both [ HTTPS] ( https ) and
1980
+ The ` 'request' ` event works identically on both [ HTTPS] [ ] and
1980
1981
HTTP/2.
1981
1982
1982
1983
### Class: http2.Http2ServerRequest
@@ -2605,7 +2606,7 @@ added: v8.4.0
2605
2606
Sends a response header to the request. The status code is a 3-digit HTTP
2606
2607
status code, like ` 404 ` . The last argument, ` headers ` , are the response headers.
2607
2608
2608
- For compatibility with [ HTTP/1] ( ) , a human-readable ` statusMessage ` may be
2609
+ For compatibility with [ HTTP/1] [ ] , a human-readable ` statusMessage ` may be
2609
2610
passed as the second argument. However, because the ` statusMessage ` has no
2610
2611
meaning within HTTP/2, the argument will have no effect and a process warning
2611
2612
will be emitted.
0 commit comments