[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libmicrohttpd] Chunked encoding POST getting a 411 error

From: Christian Grothoff
Subject: Re: [libmicrohttpd] Chunked encoding POST getting a 411 error
Date: Thu, 24 Jan 2019 05:22:35 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0

You're not incorrect, but likely the first one to try this. I don't
recall anyone ever implementing this feature for uploads. Is there a
good reason why you need it? Usually clients telling the server up-front
how big the upload is, is a good idea, so that the server can reject
uploads that are too large for some reason. I've not yet seen an
application where the client doesn't know the size of the upload (not
saying there isn't one).

On 1/24/19 3:14 AM, Kim Scarborough wrote:
> I'm using libmicrohttpd-0.9.62, and I'm having a problem with posting
> chunked-encoded files without a Content-Length header:
> POST /upload HTTP/1.1
> Host: myhost.example
> Transfer-Encoding: chunked
> Content-Type: application/vnd.fdo.journal
> HTTP/1.1 411 Length Required
> Connection: close
> Content-Length: 35
> Content-Type: text/plain
> Date: Thu, 24 Jan 2019 01:21:41 GMT
> I thought using "Transfer-Encoding: chunked" meant I didn't have to
> specify "Content-Length". Am I incorrect?

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]