Skip to content
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

bug: connection is closed too soon when doing a fetch from a nodejs app #25

Open
sandros94 opened this issue Apr 19, 2024 · 0 comments
Open

Comments

@sandros94
Copy link

sandros94 commented Apr 19, 2024

Bear with me if I'm not able to provide a reproduction, yet. Will do as soon as I'm able to.

While using a fetch library on a nodejs app, with the provided docker-compose.yml from the readme, I get a no response from the proxy. But looking at the proxy container logs I do see that the request was successfully proxied.

If I try to intentionally break the request (ex: without providing a bearer token) the proxy container responds correctly with an unauthorized data, meaning that the connection between the two does indeed work, it is just for successful proxy requests it doesn't keep on hold the incoming request.

Fetching directly openruntime-executor or any other container works as intended

@sandros94 sandros94 changed the title bug: connection is closed too early when doing a fetch from a nodejs app bug: connection is closed too soon when doing a fetch from a nodejs app May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant