rfc:cli_server_http2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:cli_server_http2 [2016/01/18 08:22] – Added Apache 2 usage of libnghttp2 daveyrfc:cli_server_http2 [2025/04/03 13:08] (current) – external edit 127.0.0.1
Line 18: Line 18:
  
   - Make it optional, allowing you to build the current HTTP/1.x cli-server and requiring no additional dependency   - Make it optional, allowing you to build the current HTTP/1.x cli-server and requiring no additional dependency
-  - Make it required+  - Make it required, but this also effectively requires libopenssl
  
 It should be noted that libnghttp2 is also used by both curl and Apache 2, making it more likely that you already have it It should be noted that libnghttp2 is also used by both curl and Apache 2, making it more likely that you already have it
Line 26: Line 26:
 In addition, we should consider adding the HTTP/2 ''SETTINGS'' to ''$_SERVER'' so we can both detect that the request is using HTTP/2 and make intelligent decisions on how the application performs (e.g. server push of multiple CSS files vs minifying/concatenating). In addition, we should consider adding the HTTP/2 ''SETTINGS'' to ''$_SERVER'' so we can both detect that the request is using HTTP/2 and make intelligent decisions on how the application performs (e.g. server push of multiple CSS files vs minifying/concatenating).
  
-We should also support the ability to do server push using HTTP headers (current community thinking is leaning towards ''Link: <resource>; rel=push'' header)+We should also support the ability to do server push using HTTP headers (current community thinking is leaning towards ''Link: <resource>; rel=preload'' header)
  
 ===== Backward Incompatible Changes ===== ===== Backward Incompatible Changes =====
rfc/cli_server_http2.1453105340.txt.gz · Last modified: 2025/04/03 13:08 (external edit)

Page Tools