-
Notifications
You must be signed in to change notification settings - Fork 114
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
Chunked response from function is blocked #49
Comments
ryskiwt
changed the title
Chunked response from function is blocked by watchdog
Chunked response from function is blocked
Feb 8, 2019
I found a hint to solve this issue in https://golang.org/src/net/http/httputil/reverseproxy.go#L335
https://golang.org/src/net/http/httputil/reverseproxy.go#L366 and https://golang.org/src/net/http/httputil/reverseproxy.go#L418 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear maintainers,
I wrote my template that is similar to https://github.com/openfaas-incubator/python-flask-template/tree/master/template/python3-flask.
The different from the original is that my template uses stream response (or, chunked response) as follows.
When I invoke a function from the template, the function does not return response chunk by chunk.
It blocks 3 seconds, and then, returns whole the response (1, 2 and 3) all at once.
Expected Behaviour
Function returns response chunk by chunk.
Current Behaviour
Function blocks 3 seconds, and then, returns whole the response all at once.
Possible Solution
The following code blocks until whole the response returned.
https://github.com/openfaas-incubator/of-watchdog/blob/bae373954932a07d89ab926457d237f03f6c60dc/executor/http_runner.go#L173
And openfaas/faas's following code also blocks, maybe.
https://github.com/openfaas/faas/blob/04d240aac26acdaf49863dbab768b4f5cb311d84/gateway/handlers/forwarding_proxy.go#L130
Steps to Reproduce (for bugs)
Your Environment
Docker version 18.09.1, build 4c52b90
Docker swarm
Linux (vagrant, vm.box = "bento/centos-7.4")
Thank you.
The text was updated successfully, but these errors were encountered: