I'm not sure I understand how PowerShell plays into this.
If you reissue a given request with Fiddler, does it work?
Is the HTTP-method really "BITS_POST" or is this just an artifact of
whatever tool you're using for display?
It *seems* like a likely explanation is that the server is expecting a
Content-Length header but the Visual Studio client isn't providing
one?
On Jun 27, 4:12 pm, Sean <
seanksulli...@gmail.com> wrote:
> I cannot find a way to successfully mimic Background Intelligent File
> Transfer (BITS) http-POSTS via Visual Studio web tests, from captured
> sessions.
>
> The unsuccessful REQUEST via VS2010 WebTest, from capturing a Fiddler
> session:
>
> HEADER:
> BITS_POSThttp://BitsWebServer/BITS/a5d70f1c-82d9-46a4-94d8-6066b54b79ec.FILE
> HTTP/1.1
>
> Accept: */*
>
> User-Agent: Microsoft BITS/7.5
>
> BITS-Packet-Type: Create-Session
>
> BITS-Supported-Protocols: {7df0354d-249b-430f-820d-3d2a9bef4931}
>
> Accept-Language: en-US
>
> Accept-Encoding: GZIP
>
> Host: v-dev-app-009
>
> Connection: Keep-Alive
>
> RESPONSE: HTTP/1.1 500 Internal Server Error
>
> --------------------------------------------------------------------------------
>
> Successful REQUEST via Microsoft supported PowerShell script (Fiddler
> captured session):
>
> HEADER:
> BITS_POSThttp://BitsWebServer/BITS/a5d70f1c-82d9-46a4-94d8-6066b54b79ec.FILE
> HTTP/1.1
>
> Accept: */*
>
> User-Agent: Microsoft BITS/7.5
>
> BITS-Packet-Type: Create-Session
>
> BITS-Supported-Protocols: {7df0354d-249b-430f-820d-3d2a9bef4931}
>
> Connection: Keep-Alive
>
> Content-Length: 0
>
> Host: v-dev-app-009
>
> RESPONSE: HTTP/1.1 200 OK
> -----------------------------------------------------------------------------------