blocks|key|1335471|text|我没有在500代码上测试过，但它可以在200,302和404等其他代码上运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1335472|response=$(curl+--write-out+'%25{http_code}'+--silent+--output+/dev/null+servername)|code-block|syntax|javascript|1335473|注意，为--write-out提供的格式应用引号引用。根据@ibai的建议，添加--head以发出仅头部请求。这将节省检索成功时的时间，因为页面内容不会被传输。|offset|length|style|CODE|1335474|entityMap^0|0|0|14|6|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I haven't tested this on a 500 code, but it works on others like 200, 302 and 404.
<pre><code>response=$(curl --write-out '%{http_code}' --silent --output /dev/null servername)
</code></pre>
Note, format provided for --write-out should be quoted.
As suggested by @ibai, add <code>--head</code> to make a HEAD only request. This will save time when the retrieval is successful since the page contents won't be transmitted.

blocks|key|1120348|text|使用netcat和awk，您可以手动处理服务器响应：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120349|if+netcat+127.0.0.1+8080+<<EOF+%7C+awk+'NR==1{if+($2+==+"500")+exit+0;+exit+1;}';+then
GET+/+HTTP/1.1
Host:+www.example.com

EOF

++++apache2ctl+restart;
fi|code-block|syntax|javascript|1120350|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|$]]

With netcat and awk you can handle the server response manually:

<pre><code>if netcat 127.0.0.1 8080 &lt;&lt;EOF | awk 'NR==1{if ($2 == "500") exit 0; exit 1;}'; then
GET / HTTP/1.1
Host: www.example.com

EOF

 apache2ctl restart;
fi
</code></pre>

blocks|key|1335599|text|尽管accepted+response是一个很好的答案，但它忽略了失败的情况。如果请求中存在错误或连接失败，curl将返回000。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1335600|url='http://localhost:8080/'
status=$(curl+--head+--location+--connect-timeout+5+--write-out+%25{http_code}+--silent+--output+/dev/null+${url})
[[+$status+==+500+]]+%7C%7C+[[+$status+==+000+]]+&&+echo+restarting+${url}+#+do+start/restart+logic|code-block|syntax|javascript|1335601|注意:这比请求的500状态检查稍微超出了一点，以确认curl甚至可以连接到服务器(即返回000)。|1335602|从它创建一个函数：|1335603|failureCode()+{
++++local+url=${1:-http://localhost:8080}
++++local+code=${2:-500}
++++local+status=$(curl+--head+--location+--connect-timeout+5+--write-out+%25{http_code}+--silent+--output+/dev/null+${url})
++++[[+$status+==+${code}+]]+%7C%7C+[[+$status+==+000+]]
}|1335604|测试获取500|1335605|failureCode+http://httpbin.org/status/500+&&+echo+need+to+restart|1335606|测试获取错误/连接失败(即000)：|1335607|failureCode+http://localhost:77777+&&+echo+need+to+start|1335608|测试未获得500|1335609|failureCode+http://httpbin.org/status/400+%7C%7C+echo+not+a+failure|1335610|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/2220646/23056^0|1I|4|1P|3|2|H|0|0|0|8|3|Q|4|18|3|0|0|0|4|3|0|0|D|3|0|0|5|3|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|F|3|G|5|H|7|1I|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1J|8|@$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|1R|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|S|3|T|5|H|7|1V|8|@]|D|@]|E|$I|J]]|$1|U|3|V|5|6|7|1W|8|@$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|W|3|X|5|H|7|1Z|8|@]|D|@]|E|$I|J]]|$1|Y|3|Z|5|6|7|20|8|@$9|21|A|22|B|C]]|D|@]|E|$]]|$1|10|3|11|5|H|7|23|8|@]|D|@]|E|$I|J]]|$1|12|3|-4|5|6|7|24|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]]]

Although the <a href="https://stackoverflow.com/a/2220646/23056">accepted response</a> is a good answer, it overlooks failure scenarios. <code>curl</code> will return <code>000</code> if there is an error in the request or there is a connection failure.

<pre class="lang-sh prettyprint-override"><code>url='http://localhost:8080/'
status=$(curl --head --location --connect-timeout 5 --write-out %{http_code} --silent --output /dev/null ${url})
[[ $status == 500 ]] || [[ $status == 000 ]] &amp;&amp; echo restarting ${url} # do start/restart logic
</code></pre>

Note: this goes a little beyond the requested <code>500</code> status check to also confirm that <code>curl</code> can even connect to the server (i.e. returns <code>000</code>).

Create a function from it:

<pre class="lang-sh prettyprint-override"><code>failureCode() {
 local url=${1:-http://localhost:8080}
 local code=${2:-500}
 local status=$(curl --head --location --connect-timeout 5 --write-out %{http_code} --silent --output /dev/null ${url})
 [[ $status == ${code} ]] || [[ $status == 000 ]]
}
</code></pre>

Test getting a <code>500</code>:

<pre class="lang-sh prettyprint-override"><code>failureCode http://httpbin.org/status/500 &amp;&amp; echo need to restart
</code></pre>

Test getting error/connection failure (i.e. <code>000</code>):

<pre class="lang-sh prettyprint-override"><code>failureCode http://localhost:77777 &amp;&amp; echo need to start
</code></pre>

Test not getting a <code>500</code>:

<pre class="lang-sh prettyprint-override"><code>failureCode http://httpbin.org/status/400 || echo not a failure
</code></pre>

blocks|key|1120468|text|curl+--write-out+"%25{http_code}\n"+--silent+--output+/dev/null+"$URL"|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1120469|很管用。如果没有，你必须点击return来查看代码本身。|unstyled|1120470|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>curl --write-out "%{http_code}\n" --silent --output /dev/null "$URL"
</code></pre>

works. If not, you have to hit return to view the code itself.

blocks|key|1120500|text|要遵循3XX重定向并打印所有请求的响应代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120501|HTTP_STATUS="$(curl+-IL+--silent+example.com+%7C+grep+HTTP+)";++++
echo+"${HTTP_STATUS}";|code-block|syntax|javascript|1120502|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|$]]

To follow 3XX redirects and print response codes for all requests:

<pre><code>HTTP_STATUS="$(curl -IL --silent example.com | grep HTTP )"; 
echo "${HTTP_STATUS}";
</code></pre>

blocks|key|1335734|text|这有助于评估http状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1335735|var=`curl+-I+http://www.example.org+2>/dev/null+%7C+head+-n+1+%7C+awk+-F"+"+'{print+$2}'`
echo+http:$var|code-block|syntax|javascript|1335736|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|$]]

this can help to evaluate http status

<pre><code>var=`curl -I http://www.example.org 2&gt;/dev/null | head -n 1 | awk -F" " '{print $2}'`
echo http:$var
</code></pre>

blocks|key|1120595|text|另一种变体：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120596|+++++++status=$(curl+-sS++-I+https://www.healthdata.gov/user/login++2>+/dev/null+%7C+head+-n+1+%7C+cut+-d'+'+-f2)
status_w_desc=$(curl+-sS++-I+https://www.healthdata.gov/user/login++2>+/dev/null+%7C+head+-n+1+%7C+cut+-d'+'+-f2-)|code-block|syntax|javascript|1120597|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|$]]

Another variation:

<pre><code> status=$(curl -sS -I https://www.healthdata.gov/user/login 2&gt; /dev/null | head -n 1 | cut -d' ' -f2)
status_w_desc=$(curl -sS -I https://www.healthdata.gov/user/login 2&gt; /dev/null | head -n 1 | cut -d' ' -f2-)
</code></pre>

blocks|key|1120645|text|这里有一个冗长但易于理解的脚本，灵感来自于nicerobot的解决方案，它只请求响应头，并避免像建议的here那样使用IFS。当它遇到响应>=+400时，它输出退回消息。这个回显可以用一个弹跳脚本来代替。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1120646|#+set+the+url+to+probe
url='http://localhost:8080'
#+use+curl+to+request+headers+(return+sensitive+default+on+timeout:+"timeout+500").+Parse+the+result+into+an+array+(avoid+settings+IFS,+instead+use+read)
read+-ra+result+<<<+$(curl+-Is+--connect-timeout+5+"${url}"+%7C%7C+echo+"timeout+500")
#+status+code+is+second+element+of+array+"result"
status=${result[1]}
#+if+status+code+is+greater+than+or+equal+to+400,+then+output+a+bounce+message+(replace+this+with+any+bounce+script+you+like)
[+$status+-ge+400++]+&&+echo+"bounce+at+$url+with+status+$status"|code-block|syntax|javascript|1120647|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2220301/how-to-evaluate-http-response-codes-from-bash-shell-script#answer-2222287|1|https://stackoverflow.com/questions/11418502/bash-string-to-array-with-ifs#answer-11418930^0|L|9|0|1F|4|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

Here comes the long-winded – yet easy to understand – script, inspired by the solution of <a href="https://stackoverflow.com/questions/2220301/how-to-evaluate-http-response-codes-from-bash-shell-script#answer-2222287" title="nice robot">nicerobot</a>, that only requests the response headers and avoids using IFS as suggested <a href="https://stackoverflow.com/questions/11418502/bash-string-to-array-with-ifs#answer-11418930" title="here">here</a>. It outputs a bounce message when it encounters a response >= 400. This echo can be replaced with a bounce-script.

<pre><code># set the url to probe
url='http://localhost:8080'
# use curl to request headers (return sensitive default on timeout: "timeout 500"). Parse the result into an array (avoid settings IFS, instead use read)
read -ra result &lt;&lt;&lt; $(curl -Is --connect-timeout 5 "${url}" || echo "timeout 500")
# status code is second element of array "result"
status=${result[1]}
# if status code is greater than or equal to 400, then output a bounce message (replace this with any bounce script you like)
[ $status -ge 400 ] &amp;&amp; echo "bounce at $url with status $status"
</code></pre>

blocks|key|1120744|text|今天我需要快速演示一些东西，然后想出了这个。我想如果有人需要类似行动要求的东西我会把它放在这里。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1120745|#!/bin/bash

status_code=$(curl+--write-out+%25{http_code}+--silent+--output+/dev/null+www.bbc.co.uk/news)

if+[[+"$status_code"+-ne+200+]]+;+then
++echo+"Site+status+changed+to+$status_code"+%7C+mail+-s+"SITE+STATUS+CHECKER"+"my_email@email.com"+-r+"STATUS_CHECKER"
else
++exit+0
fi|code-block|syntax|javascript|1120746|这将发送一个电子邮件警报的状态从200的每一个变化，所以它是愚蠢的和潜在的贪婪。为了改进这一点，我将考虑遍历几个状态代码，并根据结果执行不同的操作。|1120747|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I needed to demo something quickly today and came up with this. Thought I would place it here if someone needed something similar to the OP's request.

<pre><code>#!/bin/bash

status_code=$(curl --write-out %{http_code} --silent --output /dev/null www.bbc.co.uk/news)

if [[ "$status_code" -ne 200 ]] ; then
 echo "Site status changed to $status_code" | mail -s "SITE STATUS CHECKER" "my_email@email.com" -r "STATUS_CHECKER"
else
 exit 0
fi
</code></pre>

This will send an email alert on every state change from 200, so it's dumb and potentially greedy. To improve this, I would look at looping through several status codes and performing different actions dependant on the result.

blocks|key|1335928|text|我不喜欢这里的答案把数据和状态混为一谈。发现了这一点:您添加了-f标志以使curl失败，并从标准状态var：$？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1335929|https://unix.stackexchange.com/questions/204762/return-code-for-curl-used-in-a-command-substitution|offset|length|1335930|我不知道它是否适合这里的所有场景，但它似乎符合我的需求，而且我认为使用它要容易得多|1335931|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2R|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

i didn't like the answers here that mix the data with the status.
found this:
you add the -f flag to get curl to fail and pick up the error status code from the standard status var: $?

<a href="https://unix.stackexchange.com/questions/204762/return-code-for-curl-used-in-a-command-substitution">https://unix.stackexchange.com/questions/204762/return-code-for-curl-used-in-a-command-substitution</a>

i don't know if it's perfect for every scenario here, but it seems to fit my needs and i think it's much easier to work with

blocks|key|1335989|text|下面是我的实现，它比前面的一些答案更加冗长|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1335990|curl+https://somewhere.com/somepath+++\
--silent+\
--insecure+\
--request+POST+\
--header+"your-curl-may-want-a-header"+\
--data+@my.input.file+\
--output+site.output+\
--write-out+%25{http_code}+\
++>+http.response.code+2>+error.messages
errorLevel=$?
httpResponse=$(cat+http.response.code)


jq+--raw-output+'keys+%7C+@csv'+site.output+%7C+sed+'s/"//g'+>+return.keys
hasErrors=`grep+--quiet+--invert+errors+return.keys;echo+$?`

if+[[+$errorLevel+-gt+0+]]+%7C%7C+[[+$hasErrors+-gt+0+]]+%7C%7C+[[+"$httpResponse"+!=+"200"+]];+then
++echo+-e+"Error+POSTing+https://somewhere.com/somepath+with+input+my.input+(errorLevel+$errorLevel,+http+response+code+$httpResponse)"+>>+error.messages
++send_exit_message+#+external+function+to+send+error.messages+to+whoever.
fi|code-block|syntax|javascript|1335991|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|$]]

Here is my implementation, which is a bit more verbose than some of the previous answers

<pre><code>curl https://somewhere.com/somepath \
--silent \
--insecure \
--request POST \
--header "your-curl-may-want-a-header" \
--data @my.input.file \
--output site.output \
--write-out %{http_code} \
 &gt; http.response.code 2&gt; error.messages
errorLevel=$?
httpResponse=$(cat http.response.code)


jq --raw-output 'keys | @csv' site.output | sed 's/"//g' &gt; return.keys
hasErrors=`grep --quiet --invert errors return.keys;echo $?`

if [[ $errorLevel -gt 0 ]] || [[ $hasErrors -gt 0 ]] || [[ "$httpResponse" != "200" ]]; then
 echo -e "Error POSTing https://somewhere.com/somepath with input my.input (errorLevel $errorLevel, http response code $httpResponse)" &gt;&gt; error.messages
 send_exit_message # external function to send error.messages to whoever.
fi
</code></pre>

I have the feeling that I'm missing the obvious, but have not succeeded with <code>man [curl|wget]</code> or google ("http" makes such a bad search term). I'm looking for a quick&amp;dirty fix to one of our webservers that frequently fails, returning status code 500 with an error message. Once this happens, it needs to be restarted.

As the root cause seems to be hard to find, we're aiming for a quick fix, hoping that it will be enough to bridge the time until we can really fix it (the service doesn't need high availability)

The proposed solution is to create a cron job that runs every 5 minutes, checking <a href="http://localhost:8080/" rel="noreferrer">http://localhost:8080/</a>. If this returns with status code 500, the webserver will be restarted. The server will restart in under a minute, so there's no need to check for restarts already running.

The server in question is a ubuntu 8.04 minimal installation with just enough packages installed to run what it currently needs. There is no hard requirement to do the task in bash, but I'd like it to run in such a minimal environment without installing any more interpreters. 

(I'm sufficiently familiar with scripting that the command/options to assign the http status code to an environment variable would be enough - this is what I've looked for and could not find.)

How to evaluate http response codes from bash/shell script?

服务器

解释器

我有一种感觉，我错过了显而易见的东西，但在man [curl|wget]或google上并没有成功("http“是一个糟糕的搜索词)。我正在寻找一个快速和肮脏的修复我们的一个网站服务器，经常失败，返回状态码500与错误信息。一旦发生这种情况，就需要重新启动。由于根本原因似乎很难找到，我们的目标是快速修复，希望这将足以弥...

问如何从bash/shell脚本评估http响应码？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从bash/shell脚本评估http响应码？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从bash/shell脚本评估http响应码？
EN