-
-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Receiving FRAME_SIZE_ERROR
in complex setup
#644
Comments
dmeijboom
changed the title
Receiving
Receiving Oct 26, 2022
FRAME_SIZE_ERROR
for some serversFRAME_SIZE_ERROR
in complex setup
I'm not sure but could hyperium/hyper#2855 be related? The reverse proxy uses Snippet: let stream = self
.body
.map(|buf| buf.map(|mut buf| buf.copy_to_bytes(buf.remaining())));
request.body_mut().replace(Body::wrap_stream(stream)); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm building an alternative implementation of a (mostly) decentralised networking protocol. This protocol consists of the following services:
curl
or an application in any programming language)The traffic flow is like this (going both ways):
Both the Outway/Inway use warp for the server implementation and reqwest for the client in the reverse proxy. The configuration of reqwest is as follows:
Outway
Inway
I tried to verify this is not an issue with my reverse proxy implementation (which is very basic). To check this I used
curl
(with TLS client authentication) directly with the Inway. This works fine. So the following flow seems to work:So it seems that this is an issue between the Outway and the Inway, although I'm not 100% sure.
The error I'm getting is
BrokenPipe
inhyper
. This doesn't seem to happen when I either forcehttp1
in thereqwest::ClientBuilder
of the Outway or remove the request body stream. Not sure if it's relevant but this is how I stream the request body in the reverse proxy:Trace logs (in the Inway with
https://httpbin.org/anything
as the service endpoint):The text was updated successfully, but these errors were encountered: