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

[José Bollo]

On Thu, 24 Jan 2019 05:22:35 +0100
Christian Grothoff <address@hidden> wrote:

> 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).

I sew some. The very good use case is for sending logs as text.

Any streamed data can also need that behaviour: movies, radio, ...


> 
> 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?
> >   
>