Content-type issue

PowerShell Universal
1

We are facing an issue with the content-type passed to the GET endpoints in PSU.
As you can see below the first call is against a server running PSU and the second call against a server running UD.

What could be the issue here?
You may argue that for GET endpoints there is no need to pass the content-type in the headers however the applications calling our endpoints won’t change the way they call it.

Any help is appreciated.

image
image1587×672 29.9 KB

2

After a couple of tests and good discussion it has turned out that endpoint fails when using Powershell 5.1 as environment.

3

@adam would you please create an issue for this if you agree?
Thanks

4

This will be fixed in 3.8. It’s due a difference between ConvertTo-Json in PS7 and WinPS.

5

@adam
Sounds good. Do you perhaps have the link to the issue in your backlog?