You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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 ano 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 intendedThe text was updated successfully, but these errors were encountered: