Perry Mitchell

In the mean time you could just pass `--insecure-http-parser` to your node app, which would negate the need for this.

Streams are tricky. Are you waiting for it to finish? You could use something like [`end-of-stream`](https://www.npmjs.com/package/end-of-stream) to detect this easily. Ideally you'd want to log out all stream errors to...

@artturimatias Ok, so I tried with an example and the stream writes, but I don't get the end event at the correct moment. Here's the example I'm using: ```javascript const...

Yes in your example the Content-Type is wrong.. it should probably be `application/octet-stream`. I can't imagine why this would be. Webdav-client doesn't set content-type, so it must be getting set...

We had another issue - #147 - which might have played some part in this issue. I know it was mentioned earlier but it might be worth trying again now...

@artturimatias Please let me know if you discover otherwise. It’s hard to get streaming working perfectly.

It's good to note that you can, at least as of v4.0.0-r01, upload a file steam using `putFileContents` instead of `createWriteStream`. That being said, I'm planning to add easy access...

@simatec `putFileContents` takes a stream, so you don't need to use `fs.readFileSync`.

The `putFileContents` method supports [overriding the content length header](https://github.com/perry-mitchell/webdav-client#putfilecontents), so using this together with a stream should work. It's unfortunate that some servers require this header, as streaming is inherently...

@Freir96 There's most likely something wrong with the authentication being made.. Any chance you can record the headers when making this request? It'd be important to see what's being sent...