跳至主要内容

通过curl获取http状态码

通过curl获取网页当前的http状态码

操作实例如下:

  1. bbq@DESKTOP-SOR0NVK MINGW64 /d/gits/plan9 (main)
  2. $ curl -o /dev/null -s -w "%{http_code}" https://plan9.cn
  3. 200

说明:

  • -o 输出，定向到/dev/null
  • -s 静默模式，不显示过程
  • -w 格式化输出，相关说明可通过curl --help -w来查看
  1. bbq@DESKTOP-SOR0NVK MINGW64 /d/gits/plan9 (main)
  2. $ curl --help -w
  3.     -w, --write-out <format>
  4.             Make  curl  display  information   on  stdout  after  a   completed
  5.             transfer. The format is a string that may contain plain  text mixed
  6.             with any  number of variables.  The format  can be  specified as  a
  7.             literal "string", or you can have curl read the format from  a file
  8.             with "@filename" and  to tell curl  to read  the format from  stdin
  9.             you write "@-".
  11.             The variables present in the  output format are substituted by  the
  12.             value or  text  that  curl  thinks fit,  as  described  below.  All
  13.             variables are specified as %{variable_name} and to output a  normal
  14.             % you just write them as %%. You can output a newline by  using \n,
  15.             a carriage return with \r and a tab space with \t.
  17.             The output is  by default written  to standard  output, but can  be
  18.             changed with %{stderr} and %output{}.
  20.             Output HTTP header  values from the  transfer's most recent  server
  21.             response by using %header{name} where name is the case  insensitive
  22.             name of  the  header  (without  the  trailing  colon).  The  header
  23.             contents are  exactly  as  delivered  over  the  network  but  with
  24.             leading and trailing  whitespace and newlines  stripped off  (added
  25.             in 7.84.0).
  27.             Select a specific target destination  file to write the output  to,
  28.             by using  %output{name} (added  in curl  8.3.0) where  name is  the
  29.             full filename.  The  output  following  that  instruction  is  then
  30.             written to that file.  More than one  %output{} instruction can  be
  31.             specified in the  same write-out argument.  If the filename  cannot
  32.             be created,  curl leaves  the output  destination to  the one  used
  33.             prior to the %output{}  instruction. Use %output{>>name} to  append
  34.             data to an existing file.
  36.             This output  is done  independently  of if  the file  transfer  was
  37.             successful or not.
  39.             If the specified action or output specified with this option  fails
  40.             in any way, it does not make curl return a (different) error.
  42.             NOTE: On Windows, the %-symbol  is a special symbol used to  expand
  43.             environment variables. In  batch files, all  occurrences of %  must
  44.             be doubled  when using  this  option to  properly escape.  If  this
  45.             option is used at the command  prompt then the % cannot be  escaped
  46.             and unintended expansion is possible.
  48.             The variables available are:
  50.             certs
  52.                 Output the certificate  chain with details.  Supported only  by
  53.                 the OpenSSL,  GnuTLS, Schannel,  Rustls, and  Secure  Transport
  54.                 backends. (Added in 7.88.0)
  56.             conn_id
  58.                 The connection  identifier  last  used  by  the  transfer.  The
  59.                 connection id is unique number among all connections using  the
  60.                 same connection cache. (Added in 8.2.0)
  62.             content_type
  64.                 The Content-Type of the requested document, if there was any.
  66.             errormsg
  68.                 The error message. (Added in 7.75.0)
  70.             exitcode
  72.                 The numerical exit code of the transfer. (Added in 7.75.0)
  74.             filename_effective
  76.                 The ultimate filename  that curl  writes out to.  This is  only
  77.                 meaningful if  curl  is  told  to  write to  a  file  with  the
  78.                 --remote-name  or  --output  option.  It  is  most  useful   in
  79.                 combination with the --remote-header-name option.
  81.             ftp_entry_path
  83.                 The initial  path  curl ended  up in  when  logging on  to  the
  84.                 remote FTP server.
  86.             header{name}
  88.                 The value  of header  "name" from  the transfer's  most  recent
  89.                 server response.  Unlike  other variables,  the  variable  name
  90.                 "header" is not in  braces. For example "%header{date}".  Refer
  91.                 to --write-out remarks. (Added in 7.84.0)
  93.             header_json
  95.                 A JSON object with  all HTTP response  headers from the  recent
  96.                 transfer. Values are provided as  arrays, since in the case  of
  97.                 multiple headers  there  can  be  multiple  values.  (Added  in
  98.                 7.83.0)
  100.                 The header  names provided  in lowercase,  listed in  order  of
  101.                 appearance over the wire.  Except for duplicated headers.  They
  102.                 are grouped on the first occurrence of that header, each  value
  103.                 is presented in the JSON array.
  105.             http_code
  107.                 The  numerical  response  code  that  was  found  in  the  last
  108.                 retrieved HTTP(S) or FTP(s) transfer.
  110.             http_connect
  112.                 The numerical code that was found in the last response  (from a
  113.                 proxy) to a curl CONNECT request.
  115.             http_version
  117.                 The http version that was effectively used.
  119.             json
  121.                 A JSON object with all available keys. (Added in 7.70.0)
  123.             local_ip
  125.                 The IP  address of  the local  end of  the  most recently  done
  126.                 connection - can be either IPv4 or IPv6.
  128.             local_port
  130.                 The local port number of the most recently done connection.
  132.             method
  134.                 The http method used  in the most  recent HTTP request.  (Added
  135.                 in 7.72.0)
  137.             num_certs
  139.                 Number of server  certificates received in  the TLS  handshake.
  140.                 Supported only  by the  OpenSSL, GnuTLS,  Schannel, Rustls  and
  141.                 Secure Transport backends. (Added in 7.88.0)
  143.             num_connects
  145.                 Number of new connects made in the recent transfer.
  147.             num_headers
  149.                 The number  of  response headers  in  the most  recent  request
  150.                 (restarted at each redirect). Note that the status line IS  NOT
  151.                 a header. (Added in 7.73.0)
  153.             num_redirects
  155.                 Number of redirects that were followed in the request.
  157.             num_retries
  159.                 Number of retries  actually performed when  "--retry" has  been
  160.                 used. (Added in 8.9.0)
  162.             onerror
  164.                 The rest of the output  is only shown if the transfer  returned
  165.                 a non-zero error. (Added in 7.75.0)
  167.             output{filename}
  169.                 From this point on,  the --write-out output  is written to  the
  170.                 filename specified  in braces.  The  filename can  be  prefixed
  171.                 with ">>" to append  to the file.  Unlike other variables,  the
  172.                 variable  name  "output"   is  not  in   braces.  For   example
  173.                 "%output{>>stats.txt}". Refer  to --write-out  remarks.  (Added
  174.                 in 8.3.0)
  176.             proxy_ssl_verify_result
  178.                 The  result  of   the  HTTPS  proxy's   SSL  peer   certificate
  179.                 verification that was requested.  0 means the verification  was
  180.                 successful.
  182.             proxy_used
  184.                 Returns 1 if the previous  transfer used a proxy, otherwise  0.
  185.                 Useful to for example determine if a "NOPROXY" pattern  matched
  186.                 the hostname or not. (Added in 8.7.0)
  188.             redirect_url
  190.                 When an  HTTP request  was made  without --location  to  follow
  191.                 redirects (or when  --max-redirs is met),  this variable  shows
  192.                 the actual URL a redirect would have gone to.
  194.             referer
  196.                 The Referer: header, if there was any. (Added in 7.76.0)
  198.             remote_ip
  200.                 The remote IP address  of the most  recently done connection  -
  201.                 can be either IPv4 or IPv6.
  203.             remote_port
  205.                 The remote port number of the most recently done connection.
  207.             response_code
  209.                 The  numerical  response  code  that  was  found  in  the  last
  210.                 transfer (formerly known as "http_code").
  212.             scheme
  214.                 The  URL   scheme   (sometimes  called   protocol)   that   was
  215.                 effectively used.
  217.             size_download
  219.                 The total amount  of bytes  that were downloaded.  This is  the
  220.                 size of the body/data that was transferred, excluding headers.
  222.             size_header
  224.                 The total amount of bytes of the downloaded headers.
  226.             size_request
  228.                 The total amount of bytes that were sent in the HTTP request.
  230.             size_upload
  232.                 The total amount of bytes that were uploaded. This is  the size
  233.                 of the body/data that was transferred, excluding headers.
  235.             speed_download
  237.                 The average download speed that curl measured for the  complete
  238.                 download. Bytes per second.
  240.             speed_upload
  242.                 The average upload  speed that curl  measured for the  complete
  243.                 upload. Bytes per second.
  245.             ssl_verify_result
  247.                 The result of  the SSL peer  certificate verification that  was
  248.                 requested. 0 means the verification was successful.
  250.             stderr
  252.                 From this  point  on,  the --write-out  output  is  written  to
  253.                 standard error. (Added in 7.63.0)
  255.             stdout
  257.                 From this  point  on,  the --write-out  output  is  written  to
  258.                 standard output.  This  is the  default,  but can  be  used  to
  259.                 switch back after switching to stderr. (Added in 7.63.0)
  261.             time_appconnect
  263.                 The  time, in  seconds,  it  took  from  the  start  until  the
  264.                 SSL/SSH/etc  connect/handshake   to   the   remote   host   was
  265.                 completed.
  267.             time_connect
  269.                 The time,  in seconds, it  took from  the start  until the  TCP
  270.                 connect to the remote host (or proxy) was completed.
  272.             time_namelookup
  274.                 The time, in  seconds, it took  from the  start until the  name
  275.                 resolving was completed.
  277.             time_posttransfer
  279.                 The time it took from the start until the last byte is  sent by
  280.                 libcurl. In microseconds. (Added in 8.10.0)
  282.             time_pretransfer
  284.                 The time, in  seconds, it took  from the  start until the  file
  285.                 transfer  was   just  about   to  begin.   This  includes   all
  286.                 pre-transfer commands  and negotiations  that are  specific  to
  287.                 the particular protocol(s) involved.
  289.             time_queue
  291.                 The time, in seconds, the  transfer was queued during its  run.
  292.                 This adds the queue time  for each redirect step that may  have
  293.                 happened. Transfers may  be queued for  significant amounts  of
  294.                 time when connection  or parallel limits  are in place.  (Added
  295.                 in 8.12.0)
  297.             time_redirect
  299.                 The time,  in  seconds,  it  took  for  all  redirection  steps
  300.                 including  name  lookup,  connect,  pretransfer  and   transfer
  301.                 before  the  final  transaction  was  started.  "time_redirect"
  302.                 shows the complete execution time for multiple redirections.
  304.             time_starttransfer
  306.                 The time, in seconds,  it took from  the start until the  first
  307.                 byte was received. This includes time_pretransfer and also  the
  308.                 time the server needed to calculate the result.
  310.             time_total
  312.                 The total time, in seconds, that the full operation lasted.
  314.             tls_earlydata
  316.                 The amount of bytes that were sent as TLSv1.3 early  data. This
  317.                 is 0 if this TLS feature was not used and negative if  the data
  318.                 sent had been rejected by the server. The use of early  data is
  319.                 enabled via the command  line option "--tls-earlydata".  (Added
  320.                 in 8.12.0)
  322.             url
  324.                 The URL that was fetched. (Added in 7.75.0)
  326.             url.scheme
  328.                 The scheme part of the URL that was fetched. (Added in 8.1.0)
  330.             url.user
  332.                 The user part of the URL that was fetched. (Added in 8.1.0)
  334.             url.password
  336.                 The password  part  of the  URL  that was  fetched.  (Added  in
  337.                 8.1.0)
  339.             url.options
  341.                 The options part of the URL that was fetched. (Added in 8.1.0)
  343.             url.host
  345.                 The host part of the URL that was fetched. (Added in 8.1.0)
  347.             url.port
  349.                 The port number of the URL that was fetched. If no  port number
  350.                 was specified  and  the  URL scheme  is  known,  that  scheme's
  351.                 default port number is shown. (Added in 8.1.0)
  353.             url.path
  355.                 The path part of the URL that was fetched. (Added in 8.1.0)
  357.             url.query
  359.                 The query part of the URL that was fetched. (Added in 8.1.0)
  361.             url.fragment
  363.                 The fragment  part  of the  URL  that was  fetched.  (Added  in
  364.                 8.1.0)
  366.             url.zoneid
  368.                 The zone id part of the URL that was fetched. (Added in 8.1.0)
  370.             urle.scheme
  372.                 The scheme part of the  effective (last) URL that was  fetched.
  373.                 (Added in 8.1.0)
  375.             urle.user
  377.                 The user part  of the  effective (last) URL  that was  fetched.
  378.                 (Added in 8.1.0)
  380.             urle.password
  382.                 The  password  part  of  the  effective  (last)  URL  that  was
  383.                 fetched. (Added in 8.1.0)
  385.             urle.options
  387.                 The options part of the effective (last) URL that was  fetched.
  388.                 (Added in 8.1.0)
  390.             urle.host
  392.                 The host part  of the  effective (last) URL  that was  fetched.
  393.                 (Added in 8.1.0)
  395.             urle.port
  397.                 The port number of the  effective (last) URL that was  fetched.
  398.                 If no port number was  specified, but the URL scheme is  known,
  399.                 that scheme's default port number is shown. (Added in 8.1.0)
  401.             urle.path
  403.                 The path part  of the  effective (last) URL  that was  fetched.
  404.                 (Added in 8.1.0)
  406.             urle.query
  408.                 The query part of  the effective (last)  URL that was  fetched.
  409.                 (Added in 8.1.0)
  411.             urle.fragment
  413.                 The  fragment  part  of  the  effective  (last)  URL  that  was
  414.                 fetched. (Added in 8.1.0)
  416.             urle.zoneid
  418.                 The zone id part of the effective (last) URL that  was fetched.
  419.                 (Added in 8.1.0)
  421.             urlnum
  423.                 The URL  index number  of this  transfer, 0-indexed.  Unglobbed
  424.                 URLs share the  same index  number as the  origin globbed  URL.
  425.                 (Added in 7.75.0)
  427.             url_effective
  429.                 The URL that was fetched  last. This is most meaningful if  you
  430.                 have told curl to follow location: headers.
  432.             xfer_id
  434.                 The numerical identifier of  the last transfer  done. -1 if  no
  435.                 transfer has been started yet  for the handle. The transfer  id
  436.                 is  unique  among  all  transfers  performed  using  the   same
  437.                 connection cache. (Added in 8.2.0)
  439.             If --write-out is  provided several  times, the last  set value  is
  440.             used.
  442.             Example:
  443.              curl -w '%{response_code}\n' https://example.com
  445.             See also --verbose and --head.
标签：

评论

发表评论

此博客中的热门博文

Shell 文件包含

  和其他语言一样，Shell 也可以包含外部脚本。这样可以很方便的封装一些公用的代码作为一个独立的文件。 Shell 文件包含的语法格式如下： . filename # 注意点号(.)和文件名中间有一空格 或 source filename 实例 创建两个 shell 脚本文件。 test1.sh 代码如下： #!/bin/bash # author:菜鸟教程 # url:www.runoob.com url = "http://www.runoob.com" test2.sh 代码如下： #!/bin/bash # author:菜鸟教程 # url:www.runoob.com #使用 . 号来引用test1.sh 文件 . ./ test1 . sh # 或者使用以下包含文件代码 # source ./test1.sh echo "菜鸟教程官网地址：$url" 接下来，我们为 test2.sh 添加可执行权限并执行： $ chmod + x test2 . sh $ ./ test2 . sh 菜鸟教程官网地址： http : //www.runoob.com 注： 被包含的文件 test1.sh 不需要可执行权限。
发表评论
阅读全文

Shell 输入/输出重定向

  大多数 UNIX 系统命令从你的终端接受输入并将所产生的输出发送回​​到您的终端。一个命令通常从一个叫标准输入的地方读取输入，默认情况下，这恰好是你的终端。同样，一个命令通常将其输出写入到标准输出，默认情况下，这也是你的终端。 重定向命令列表如下： 命令 说明 command > file 将输出重定向到 file。 command < file 将输入重定向到 file。 command >> file 将输出以追加的方式重定向到 file。 n > file 将文件描述符为 n 的文件重定向到 file。 n >> file 将文件描述符为 n 的文件以追加的方式重定向到 file。 n >& m 将输出文件 m 和 n 合并。 n <& m 将输入文件 m 和 n 合并。 << tag 将开始标记 tag 和结束标记 tag 之间的内容作为输入。 需要注意的是文件描述符 0 通常是标准输入（STDIN），1 是标准输出（STDOUT），2 是标准错误输出（STDERR）。 输出重定向 重定向一般通过在命令间插入特定的符号来实现。特别的，这些符号的语法如下所示: command1 > file1 上面这个命令执行command1然后将输出的内容存入file1。 注意任何file1内的已经存在的内容将被新内容替代。如果要将新内容添加在文件末尾，请使用>>操作符。 实例 执行下面的 who 命令，它将命令的完整的输出重定向在用户文件中(users): $ who > users 执行后，并没有在终端输出信息，这是因为输出已被从默认的标准输出设备（终端）重定向到指定的文件。 你可以使用 cat 命令查看文件内容： $ cat users _mbsetupuser console Oct 31 17 : 35 tianqixin console Oct 31 17 : 35 tianqixin ttys000 Dec 1 11 : 33 输出重定向会覆盖文件内容，请看下面的例子： $ echo "菜鸟教程：www.runoob.com" > users $ cat users 菜鸟教程：...
发表评论
阅读全文

Shell 函数

  linux shell 可以用户定义函数，然后在shell脚本中可以随便调用。 shell中函数的定义格式如下： [   function   ]  funname  [ ( ) ] {     action;      [ return  int; ] } 说明： 1、可以带  function fun()  定义，也可以直接  fun()  定义,不带任何参数。 2、参数返回，可以显示加： return  返回，如果不加，将以最后一条命令运行结果，作为返回值。  return  后跟数值  n(0-255) . 下面的例子定义了一个函数并进行调用： 实例 #!/bin/bash # author:菜鸟教程 # url:www.runoob.com demoFun ( ) {      echo   "这是我的第一个 shell 函数!" } echo   "-----函数开始执行-----" demoFun echo   "-----函数执行完毕-----" 输出结果： -----函数开始执行----- 这是我的第一个 shell 函数! -----函数执行完毕----- 下面定义一个带有  return  语句的函数： 实例 #!/bin/bash # author:菜鸟教程 # url:www.runoob.com funWithReturn ( ) {      echo   "这个函数会对输入的两个数字进行相加运算..."      echo   "输入第一个数字: "      read  aNum      echo   "输入第二个数字: "      read  anotherNum      echo   "两个数字分别为  ...
发表评论
阅读全文