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

2019-01-24 Thread Kim Scarborough
On 1/24/19 1:05 PM, Christian Grothoff wrote: > This most certainly is something that should be fixed in libmicrohttpd > and not in systemd. In fact, likely it cannot be fixed in systemd if I > am not mistaken. > > If you are able to work on C code, the answer probably is to go into the > MHD code

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

2019-01-24 Thread Christian Grothoff
This most certainly is something that should be fixed in libmicrohttpd and not in systemd. In fact, likely it cannot be fixed in systemd if I am not mistaken. If you are able to work on C code, the answer probably is to go into the MHD code where we test for content-length on upload, also add a ch

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

2019-01-24 Thread Kim Scarborough
It's actually systemd doing this. It uses libmicrohttpd to listen for incoming journal messages. I'm not sure why it doesn't send sizes in the header for outgoing messages. I mainly just want to get systemd journal forwarding working. Would it be more to the point to open a bug with the systemd pe

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

2019-01-24 Thread José Bollo
On Thu, 24 Jan 2019 05:22:35 +0100 Christian Grothoff 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

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

2019-01-23 Thread Christian Grothoff
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