[Http.fs bug] error with uploading request body

[saneman1]

I do PUT http request with some body, size about 1MB.
The server immediately responds with error status code (409 Conflict), I see it in the traces. After upload of the request body is complete, an error occurs:

WebException: The underlying connection was closed: An unexpected error occurred on a receive.
IOException: Unable to read data from the transport connection

exception raised at function getResponseFromBeginEnd

When size of payload request body less 1MB all ok.
The cause of the problem the following - by the end of the uploading body server already closes the connection.

How can I work around this issue and retrieve the actual response from the server?

thx, for the library, very usefull !

[ovatsus]

Can you try to get a code snippet that reproduces the problem?
/cc @baronfel

[baronfel]

It'll be at least 5 hours until I can look at this (traveling and whatnot) but I definitely will when I get back to my computer.

[saneman1]

code snippet

open FSharp.Data
open System.IO

let test () = 
    let resp = Http.Request(
                "https://somewebdav-server/dir1/file1", //server name for example
                httpMethod = "PUT",
                headers = [ 
                    HttpRequestHeaders.ContentType "application/binary"
                    HttpRequestHeaders.BasicAuth "user" "pass"
                ],
                silentHttpErrors = true,
                body = BinaryUpload (File.ReadAllBytes("c:\\tmp\sample.zip"))
              )
    match resp.StatusCode with
    | 201 -> "ok" //all ok
    
   // In my case, I expect this response (and server response this), but exception raised
    | 409 -> "parent directory absent"  // no direcory

ps. sorry, but can't give credential for real server

[ovatsus]

Hey Chet, I didn't mean to put any kind of pressure on you, look at this whenever it's convenient, remember this is open source, not work :)

[baronfel]

@ovatsus no worries, it's all internal pressure. I feel a tiny sense of ownership/responsibility for breaking it in the first place :)

[ovatsus]

This one doesn't seem related to your change, probably was already broken.
@saneman1 , did this work in 2.3.3 and got broken on 2.4.0/2.41, or does it fail on both?

[saneman1]

@ovatsus , I try only in latests version, but suppose this don't work in all.
Becouse problem in HttpWebRequest / HttpWebResponse.
I can found post about a similar problem

[saneman1]

Idealy, should cancel transmit request body (if server already send response), but I can't found a way to do it.