mod_h2: mod_proxy_http2: gRPC bi-directional messages stuck
Hi,
maybe you can help me out, I am using gRPC bi-directional messaging with grpc-dotnet. When I directly connect client and server, the messages from the client are streamed to the server without any problems. Once I change the client configuration to connect over the mod_proxy_http2 port, the messages are stuck. It seems like they are buffered because once I start sending messages from the server to the client, sometimes the client messages are delivered, too (depending on the timing) and when I shut down the gRPC server, messages also get delivered sometimes.
Here is my apache configuration:
Protocols h2
SSLProxyEngine On
<Location /tunnel.TunnelMessaging>
Require all granted
ProxyPass h2://localhost:5001/tunnel.TunnelMessaging retry=0
ProxyPassReverse https://localhost:5001/tunnel.TunnelMessaging
</Location>
And the debug log output:
- Sending the message which is not received: apache.log
- Logs when shutting down gRPC server: shutting_down_grpc_server.log
Any help would be appreciated!
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 26 (14 by maintainers)
Commits related to this issue
- * mod-h2 always flushes input DATA to the stream, so a running task (if there is one) can access it immediately. Curious if this alone addresses #207 * Eliminated some Python deprecation warnings... — committed to icing/mod_h2 by deleted user 4 years ago
- test: - added test case for #207 using new h2test module's echo handler - reqeust body data is arriving at handler, but output is still buffered and does not reach client. TODO. — committed to icing/mod_h2 by deleted user 4 years ago
- * new option 'H2OutputBuffering on/off' which controls the buffering of stream output. The default is on, which is the behaviour of older mod-h2 versions. When off, all bytes are made available... — committed to icing/mod_h2 by deleted user 4 years ago
- *) mod_http2: sync with github standalone version 1.15.17 - Log requests and sent the configured error response in case of early detected errors like too many or too long headers. [Ruedi... — committed to apache/httpd by icing 3 years ago
- Update to 2.4.27 Changes with Apache 2.4.47 *) mod_dav_fs: Improve logging output when failing to open files for writing. PR 64413. [Bingyu Shen <ahshenbingyu gmail.com>] *) mod_http2: F... — committed to clearlinux-pkgs/httpd by phmccarty 3 years ago
- ASF 2.4.47 changes: *) mod_dav_fs: Improve logging output when failing to open files for writing. PR 64413. [Bingyu Shen < ahshenbingyu gmail.com >] *) mod_http2: Fixed a race condition t... — committed to nono303/win-build-scripts by deleted user 3 years ago
- apache: update to 2.4.48. Changes with Apache 2.4.48 *) mod_proxy_wstunnel: Add ProxyWebsocketFallbackToProxyHttp to opt-out the fallback to mod_proxy_http for WebSocket upgrade and tunneling... — committed to NetBSD/pkgsrc by deleted user 3 years ago
- apache: update to 2.4.48. Changes with Apache 2.4.48 *) mod_proxy_wstunnel: Add ProxyWebsocketFallbackToProxyHttp to opt-out the fallback to mod_proxy_http for WebSocket upgrade and tunneling... — committed to TritonDataCenter/pkgsrc by deleted user 3 years ago
Thanks for the offer. It has been second on my list of things for the last week. Let me get another look, maybe I find a good approach or can give you some pointers.
If I make a test implementation of such a feature, can you build from here and verify it?