Repository navigation
Invoke-RestMethod does not count on Content-Type field. Broken compared to PS 5.0. #2245
Description
Steps to reproduce
$ Invoke-RestMethod -Uri https://httpbin.org/robots.txt
Expected behavior
Return content. Or at least behave the same as in PowerShell 5.0.
Actual behavior
Invoke-RestMethod : Unexpected character encountered while parsing value: U. Path '', line 0, position 0.
At line:1 char:1
- Invoke-RestMethod -Uri https://httpbin.org/robots.txt
-
- CategoryInfo : NotSpecified: (:) [Invoke-RestMethod], JsonReaderException - FullyQualifiedErrorId : Newtonsoft.Json.JsonReaderException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand
Environment data
> $PSVersionTable
Name Value
---- -----
PSVersion 6.0.0-alpha
PSEdition Core
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 3.0.0.0
GitCommitId v6.0.0-alpha.9
CLRVersion
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1powershell 6.0.0-alpha.9-1
Reacted by Ed Ilyin and zipcube
Activity
[-]Invoke-RestMethod do not rely on `Content-Type` field[/-][+]Invoke-RestMethod do not rely on `Content-Type` field. Broken compared to PS 5.0.[/+][-]Invoke-RestMethod do not rely on `Content-Type` field. Broken compared to PS 5.0.[/-][+]Invoke-RestMethod does not count on `Content-Type` field. Broken compared to PS 5.0.[/+]ed-ilyin commentedon Sep 22, 2016
Exactrly same for me
nmbradford commentedon Nov 7, 2016
I have similar issues talking to an XML api. I've tried with -ContentType "application/xml" and with Content-Type set in the request header with same result in both cases. The exception I get is :
Note - Interesting that JsonReader is involved in parsing an xml response?
chelnak commentedon Jan 6, 2017
We are seeing a similar issue (Logged here: jakkulabs/PowervRA#97).
The response content type is text/yaml but you can clearly see it's trying to use Newtonsofts Json library.
2xmax commentedon Feb 7, 2017
looks like it was fixed by #2862
joeyaiello commentedon Feb 7, 2017
Max Maximov (@2xmax): Thanks! Looks like the original issues were fixed already :)
jonathanmedd commentedon Feb 8, 2017
Excellent - thanks Max Maximov (@2xmax) ! We have been able to close one of our issues being able to support PowerShell Core thanks to your fix: jakkulabs/PowervRA#97