Hi Henrik, Amos and folks:
> That's the wrong approach. What is needed is to add support for chunked > encoding in the request path. Currently only supported in the response > path. Ok, but which should be the 'right' point to add or mangle a custom request header before it gets processed ? thanks in advance. Lucas Brasilino
