Benoit Chesneau
Benoit Chesneau
we can have a pattern that just place needed headers instead. I will think about it
@nerdyworm 👍 if you have some time for it don't hesitate to send me a PR for it, otherwise I will do that sometimes this week
@phylake you need to read the body. If not the socket won't be released to the pool. Try the following: ```erlang lists:foreach(fun(I) -> timer:sleep(500), io:format("req ~p~n",[I]), {ok, _Status, _Headers, _Body}...
@phylake same for all connections. You need to read the response in any case to release the socket. This is how it works currently to prevent any resource consumption. (you...
@phylake late answer, but yes get should not accept a body. It will need some changes in the way CRUD calls are handled. I will take care about newxt release.
mmm good idea! I think it implies to find the right way to handle the different way to negociate with the proxy, so a proxy can be just a backend....
do you mean receiving immediately a partial chunk? Normally it is expected to receive the whole chunk , not really for security reason but because some API just use it...
You should go next to actually redirect the reauest. Redirection should probably handled before though. It will be fixed in the next release.
Did some test. I was wrong. Since you are streaming the body, it's not kept around and there are no way yet to resend it. So the status is simply...
why did you close the issue?