blocks|key|2995508|text|虽然是一个旧线程，但这里是cmdlets+-WebRequest和Invoke-RestMethod问题的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995509|这个问题已经困扰我很长一段时间了。由于所有4xx和5xx响应都会生成异常，因此您必须捕获该异常，然后才能从那里提取响应。像这样使用它：|2995510|$resp+=+try+{+Invoke-WebRequest+...+}+catch+{+$_.Exception.Response+}|code-block|syntax|javascript|2995511|现在，$resp总是包含您喜欢的所有内容。|2995512|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Although an old thread, here an answer to the problem with the cmdlets Invoke-WebRequest and Invoke-RestMethod.

This one has bothered me for quite some time. As all 4xx and 5xx responses are generating an exception, you have to catch that one and then you are able to extract the Response from there though. Use it like this:

<pre><code>$resp = try { Invoke-WebRequest ... } catch { $_.Exception.Response }
</code></pre>

Now $resp always contains everything you like.

blocks|key|174574|text|另一个答案确实得到了响应，但您需要一个额外的步骤来获取响应的实际正文，而不仅仅是头部。下面是一个代码片段：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|174575|try+{
++++++++$result+=+Invoke-WebRequest+...
}
catch+{
++++++++$result+=+$_.Exception.Response.GetResponseStream()
++++++++$reader+=+New-Object+System.IO.StreamReader($result)
++++++++$reader.BaseStream.Position+=+0
++++++++$reader.DiscardBufferedData()
++++++++$responseBody+=+$reader.ReadToEnd();
}|code-block|syntax|javascript|174576|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The other answer does get you the response, but you need an additional step to get the actual body of the response, not just the headers. Here is a snippet:

<pre><code>try {
 $result = Invoke-WebRequest ...
}
catch {
 $result = $_.Exception.Response.GetResponseStream()
 $reader = New-Object System.IO.StreamReader($result)
 $reader.BaseStream.Position = 0
 $reader.DiscardBufferedData()
 $responseBody = $reader.ReadToEnd();
}
</code></pre>

blocks|key|2782934|text|为了寻找我的问题的答案，我找到了这个帖子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2782935|这些解决方案对我有效，但我必须添加两行新代码：|2782936|+$reader.BaseStream.Position+=+0
+$reader.DiscardBufferedData()|code-block|syntax|javascript|2782937|谢谢!|2782938|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Searching an answer for my problem I found this thread.

These solution worked for me, but I had to add two new line:

<pre><code> $reader.BaseStream.Position = 0
 $reader.DiscardBufferedData()
</code></pre>

Thanks!

blocks|key|2995536|text|此解决方案不再适用于PowerShell+6-它不支持GetResponseStream()。相反，请使用|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2995537|try+{
++++$result+=+Invoke-WebRequest+...
}
catch+{
++++$_.ErrorDetails.Message
}|code-block|syntax|javascript|2995538|我写了一个简短的助手函数来支持PowerShell+6和更早的版本：|2995539|function+ParseErrorForResponseBody($Error)+{
++++if+($PSVersionTable.PSVersion.Major+-lt+6)+{
++++++++if+($Error.Exception.Response)+{++
++++++++++++$Reader+=+New-Object+System.IO.StreamReader($Error.Exception.Response.GetResponseStream())
++++++++++++$Reader.BaseStream.Position+=+0
++++++++++++$Reader.DiscardBufferedData()
++++++++++++$ResponseBody+=+$Reader.ReadToEnd()
++++++++++++if+($ResponseBody.StartsWith('{'))+{
++++++++++++++++$ResponseBody+=+$ResponseBody+%7C+ConvertFrom-Json
++++++++++++}
++++++++++++return+$ResponseBody
++++++++}
++++}
++++else+{
++++++++return+$Error.ErrorDetails.Message
++++}
}

try+{
++++$result+=+Invoke-WebRequest+...
}
catch+{
++++ParseErrorForResponseBody($_)
}|2995540|entityMap^0|R|J|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

This solution no longer works with PowerShell 6 - it does not support <code>GetResponseStream()</code>. Instead use

<pre><code>try {
 $result = Invoke-WebRequest ...
}
catch {
 $_.ErrorDetails.Message
}
</code></pre>

I wrote a short helper function to support PowerShell 6 and earlier:

<pre><code>function ParseErrorForResponseBody($Error) {
 if ($PSVersionTable.PSVersion.Major -lt 6) {
 if ($Error.Exception.Response) { 
 $Reader = New-Object System.IO.StreamReader($Error.Exception.Response.GetResponseStream())
 $Reader.BaseStream.Position = 0
 $Reader.DiscardBufferedData()
 $ResponseBody = $Reader.ReadToEnd()
 if ($ResponseBody.StartsWith('{')) {
 $ResponseBody = $ResponseBody | ConvertFrom-Json
 }
 return $ResponseBody
 }
 }
 else {
 return $Error.ErrorDetails.Message
 }
}

try {
 $result = Invoke-WebRequest ...
}
catch {
 ParseErrorForResponseBody($_)
}
</code></pre>

blocks|key|2783098|text|请注意，$_.ErrorDetails.Message并不是原始的响应体，它是Florial对答案提供程序的扩展。一个HTML标签移除正则表达式被用来使响应更容易阅读github+link。由于流位于第1535行，因此当前无法检索原始响应体。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2783099|解决方法是使用dotnet而不是Invoke-WebRequest+HttpClient来获取原始响应|2783100|$url+=+"http://localhost"
$client+=+[System.Net.Http.HttpClient]::new()
$request+=+[System.Net.Http.HttpRequestMessage]::new([System.Net.Http.HttpMethod]::Post,+$url)
$request.Content+=+[System.Net.Http.StringContent]::new("Hello+World",+[System.Text.Encoding]::UTF8,+"plain/text")

$result+=+$client.SendAsync($request).GetAwaiter().GetResult()
$content+=+$result.Content.ReadAsStringAsync().GetAwaiter().GetResult()

Write-Verbose+$content+-Verbose|code-block|syntax|javascript|2783101|powershell核心github的问题是here|2783102|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/WebCmdlet/Common/WebRequestPSCmdlet.Common.cs#L1525|1|https://github.com/PowerShell/PowerShell/issues/5555^0|4|N|2B|B|0|0|G|H|Y|A|0|0|M|4|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|19|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|O|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

Please note as an extension to the answer provider by Florial Feldhaus the <code>$_.ErrorDetails.Message</code> is not the original response body.
An HTML tag removal regex is used to make the response easier to read <a href="https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/WebCmdlet/Common/WebRequestPSCmdlet.Common.cs#L1525" rel="nofollow noreferrer">github link</a>. Since the stream is disposed on line 1535 there is currently no way to retrieve the original response body.
The work around is to use the dotnet <code>HttpClient</code> to get the original response instead of using the <code>Invoke-WebRequest</code> cmdlet
<pre><code>$url = &quot;http://localhost&quot;
$client = [System.Net.Http.HttpClient]::new()
$request = [System.Net.Http.HttpRequestMessage]::new([System.Net.Http.HttpMethod]::Post, $url)
$request.Content = [System.Net.Http.StringContent]::new(&quot;Hello World&quot;, [System.Text.Encoding]::UTF8, &quot;plain/text&quot;)

$result = $client.SendAsync($request).GetAwaiter().GetResult()
$content = $result.Content.ReadAsStringAsync().GetAwaiter().GetResult()

Write-Verbose $content -Verbose
</code></pre>
The powershell core github issue is <a href="https://github.com/PowerShell/PowerShell/issues/5555" rel="nofollow noreferrer">here</a>

blocks|key|2783117|text|我一直在专门使用Invoke-RestMethod+--因为它可能是Invoke-WebRequest的包装器，下面的信息可能会很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2783118|您需要捕获异常，然后从response获取响应流，如下所示。|2783119|++++try
++++{
++++++++$response+=+Invoke-RestMethod+Method+Get+uri+"$($uri)"+-Headers+$headers
++++++++return+$response
++++}
++++catch
++++{
++++++++Write-Host+"Exception+details:+"
++++++++$e+=+$_.Exception
++++++++Write-Host+("`tMessage:+"+%2B+$e.Message)
++++++++Write-Host+("`tStatus+code:+"+%2B+$e.Response.StatusCode)
++++++++Write-Host+("`tStatus+description:+"+%2B+$e.Response.StatusDescription)

++++++++Write-Host+"`tResponse:+"+-NoNewline
++++++++$memStream+=+$e.Response.GetResponseStream()
++++++++$readStream+=+New-Object+System.IO.StreamReader($memStream)
++++++++while+($readStream.Peek()+-ne+-1)+{
++++++++++++Write-Host+$readStream.ReadLine()
++++++++}
++++++++$readStream.Dispose();
++++}|code-block|syntax|javascript|2783120|参考：https://social.technet.microsoft.com/Forums/windowsserver/en-US/7d838d53-bfd5-4706-b0df-c4bee2d00412/using-memorystream-and-textreader|offset|length|2783121|entityMap|0|LINK|mutability|MUTABLE|url|https://social.technet.microsoft.com/Forums/windowsserver/en-US/7d838d53-bfd5-4706-b0df-c4bee2d00412/using-memorystream-and-textreader^0|0|0|0|3|3Q|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I have been using Invoke-RestMethod exclusively - and since it might be a wrapper for Invoke-WebRequest, the following information might be useful.
You need to catch the exception and then get the response stream from Response like so.
<pre><code> try
 {
 $response = Invoke-RestMethod Method Get uri &quot;$($uri)&quot; -Headers $headers
 return $response
 }
 catch
 {
 Write-Host &quot;Exception details: &quot;
 $e = $_.Exception
 Write-Host (&quot;`tMessage: &quot; + $e.Message)
 Write-Host (&quot;`tStatus code: &quot; + $e.Response.StatusCode)
 Write-Host (&quot;`tStatus description: &quot; + $e.Response.StatusDescription)

 Write-Host &quot;`tResponse: &quot; -NoNewline
 $memStream = $e.Response.GetResponseStream()
 $readStream = New-Object System.IO.StreamReader($memStream)
 while ($readStream.Peek() -ne -1) {
 Write-Host $readStream.ReadLine()
 }
 $readStream.Dispose();
 }
</code></pre>
Reference: <a href="https://social.technet.microsoft.com/Forums/windowsserver/en-US/7d838d53-bfd5-4706-b0df-c4bee2d00412/using-memorystream-and-textreader" rel="nofollow noreferrer">https://social.technet.microsoft.com/Forums/windowsserver/en-US/7d838d53-bfd5-4706-b0df-c4bee2d00412/using-memorystream-and-textreader</a>

Invoke-RestMethod call returns only very unhelpful exception below and does not (as far as I can tell) allow you to collect the body content (JSON object shown in fiddler trace results). This seems a pretty bad implementation if so because http 500 definition is pretty specific that client should return the body of the response to help troubleshoot... Am I missing something? 

<pre><code>invoke-restmethod -method Post -uri "https://api-stage.enviance.com/ver2/EqlService.svc/eql" -Body (ConvertTo-Json $eqlhash) -Headers @{"Authorization"="Enviance $session"}
</code></pre>

<blockquote>
 invoke-restmethod : The remote server returned an error: (500)
 Internal Server Error. At line:1 char:9...
</blockquote>

Fiddler trace below 

<blockquote>
 HTTP/1.1 500 Internal Server Error Connection: close Date: Thu, 12 Sep
 2013 17:35:00 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET
 X-AspNet-Version: 2.0.50727 EnvApi-Version: 2.0,2.0
 EnvApi-Remaining-Calls: 994,994 EnvApi-Remaining-Interval: 2684,2684
 Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type:
 text/csv; charset=utf-8
 
 {"errorNumber":0,"message":"Current user has no rights to retrieve
 data from table 'CustomFieldTemplate'"}
</blockquote>

How to get Powershell Invoke-Restmethod to return body of http 500 code response

服务器

JSON

Invoke-RestMethod调用在下面只返回非常无用的异常，并且(据我所知)不允许您收集主体内容(在fiddler跟踪结果中显示的JSON对象)。如果是这样的话，这似乎是一个相当糟糕的实现，因为http 500的定义非常具体，客户端应该返回响应的正文以帮助解决问题……我是不是遗漏了什么？invoke-restme...

问如何让Powershell Invoke-Restmethod返回http 500代码响应的正文
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让Powershell Invoke-Restmethod返回http 500代码响应的正文EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让Powershell Invoke-Restmethod返回http 500代码响应的正文
EN