plans for chunked encoding

[Luka Perkov]

Hi Maxim,

On Fri, Nov 16, 2012 at 02:17:58PM +0100, Luka Perkov wrote:
> On Fri, Nov 16, 2012 at 03:48:55PM +0400, Maxim Dounin wrote:
> > > On Fri, Oct 19, 2012 at 06:13:10PM +0400, Maxim Dounin wrote:
> > > > > I'm wondering if there is any work done on this already ? If so I could
> > > > > test some patches...
> > > > 
> > > > I'll post it here once there is something to test.
> > > 
> > > Thank you.
> > 
> > JFYI, chunked request body patches are available here:
> > 
> > http://mailman.nginx.org/pipermail/nginx-devel/2012-November/002961.html
> > 
> > Review and testing appreciated.
> 
> Thank you for the patches. I'll test them this weekend (or early next
> week) and I'll give you my feedback after that.

I have started testing your patches. I'm working on dummy module for
dealing with post requests, but in the meantime I have a question.

This is the dummy post data:

$ cat > /tmp/post_data << EOF
test post data
EOF

This is what I have tested:

$ curl -v -X GET http://127.0.0.1:80/

Returns 404 in headers and html body as expected.

$ curl -v -X POST -d "@/tmp/post_data" http://127.0.0.1:80/

Returns 404 in headers and html body as expected.

$ curl -v -X POST -d "@/tmp/post_data" --header "Transfer-Encoding: chunked" http://127.0.0.1:80/

Returns 404 in headers and html body as expected.

$ curl -v -X POST -d "@/dev/null" http://127.0.0.1:80/

Returns 404 in headers and html body as expected.

$ curl -v -X POST -d "@/dev/null" --header "Transfer-Encoding: chunked" http://127.0.0.1:80/

Returns 404 in headers but 500 in html body. Is this how it's supposed to be ?

Luka