CODEWITHSUNDEEP
powershellpowershell-3.0
irl_irl
irl_irl

Reputation: 3975

Invoke-RestMethod: You must write ContentLength bytes to the request stream

I am trying to upload a file to a URL. I have tried both these approaches:

Invoke-RestMethod -Uri $uploadUrl -Method Put -Headers $uploadHdrs -InFile $uploadFilePath

Invoke-RestMethod -Uri $uploadUrl -Method Put -body $uploadFileBody -Headers $uploadHdrs

Error I am getting:

Invoke-RestMethod : You must write ContentLength bytes to the request stream
before calling [Begin]GetResponse.

If I add in the -TransferEncoding param, I get errors from the server saying unsupported.

What can I do to include the content length?

Upvotes: 2

Views: 3586

Answers (1)

Burt_Harris
Burt_Harris

Reputation: 6874

I think you'll need to use a different command, like Invoke-WebRequest or even better call the .NET WebClient.UploadFile() or .UploadData methods directly from PowerShell.

While REST methods might conceptually include uploading files, that doesn't mean that the Invoke-WebRequest command has been tested as supporting your scenario. I'd suggest going lower-level (like WebClient) because we know more scenarios have been tested (by the larger .NET team), and there are a wide variety of methods on WebClient for supporting specific scenarios.

One example you might find helpfull in how to invoke these methods from PowerShell is at https://social.technet.microsoft.com/Forums/windowsserver/en-US/0c268c7e-674c-49bc-9933-a87a95f8f44c/powershell-webclientuploadfile?forum=winserverpowershell

P.S. The message your are getting about the request stream is coming from an even lower level .NET API, but WebClient is simpler to use, should take care of setting ContentLength properly and hopefully is "just right" for your need.

Upvotes: 1

Related Questions