rfc:cli_server_http2

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rfc:cli_server_http2 [2016/01/09 06:15]
davey Remove SSL dependency wrongness
rfc:cli_server_http2 [2017/09/22 13:28] (current)
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 curland therefore if you're doing HTTP/work and have curl, 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
  
 With either implementation, we can also make HTTP/2 always enabled (if built in), or we can make it de/activated with a flag, such as: ''--[no-]http2''. I believe we **should** have this flag as it makes it possible to test HTTP/1.x fallback for HTTP/2 clients, as well as HTTP/2. With either implementation, we can also make HTTP/2 always enabled (if built in), or we can make it de/activated with a flag, such as: ''--[no-]http2''. I believe we **should** have this flag as it makes it possible to test HTTP/1.x fallback for HTTP/2 clients, as well as HTTP/2.
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.1452320149.txt.gz · Last modified: 2017/09/22 13:28 (external edit)