Changes between Initial Version and Version 1 of Ticket #1909, comment 3


Ignore:
Timestamp:
01/02/20 02:16:06 (22 months ago)
Author:
thexeos@…

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1909, comment 3

    initial v1  
    1 grepping through the debug logs, there are no mentions of word `push` anywhere. I'll provide more insight into the setup, I think that might be the cause of this: there is HAProxy listening on public port receiving HTTP/2 over TLS. It performs offloading and routes requests to local or remote (same rack) nginx instances exclusively with "proto h2" options (meaning no ALPN used, no SSL verification, practically making it h2c). On production system, there is an application running (fastcgi), which is reading custom headers set by HAProxy to determine if HTTP/2 was used by the client, and if so it adds the `Link` header to response.
     1grepping through the debug logs, there are no mentions of word `push` anywhere. I'll provide more insight into the setup, I think that might be the cause of this: there is HAProxy listening on public port receiving HTTP/2 over TLS. It performs offloading and routes requests to local or remote (same rack, over TCP) nginx instances exclusively with "proto h2" options (meaning no ALPN used, no SSL verification, practically making it h2c). On production system, there is an application running (fastcgi), which is reading custom headers set by HAProxy to determine if HTTP/2 was used by the client, and if so it adds the `Link` header to response.
    22
    33In debug log, there is `http2 header: ":scheme: https"`, so I am wondering if there is mismatch between `:scheme` and nginx receiving h2c? And if so, what is the correct solution here?