Errors reported by CheckUpDown

Errors reported by CheckUpDown

Errors reported by CheckUpDown

Introduction to errors

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

  • Obtain an IP address from the IP name of your site (the site URL without the leading ‘http://’). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  • Open an IP socket connection to that IP address.
  • Write an HTTP data stream through that socket.
  • Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

An error may occur in any of the above steps. Our CheckUpdown robot isolates any error and reports it as an error code for your account (as a clickable link) along with details of when the error was detected.

The error codes the client may receive are given below – follow the URL for each to see further discussion of the error and what further action we recommend.

0?? errors

Errors with a code in the range 001-099 indicate a fundamental failure to communicate, typically in the early steps above. Note these errors are not defined in the HTTP protocol – they are specific to our CheckUpDown service.

001 – Unknown Host
002 – I/O Exception
003 – Undefined HTTP Status Code
004 – Bad URL
005 – Host not reachable
006 – No connection
007 – I/O Interrupt
008 – Socket failure
009 – SSL secure socket failure
010 – Check word not found
011 – Socket Timeout

3?? errors

Errors with a code in the range 300-399 indicate a redirection of the Web site URL. As of September 2000, CheckUpDown follows some URL redirections (301, 302, 303, 307) automatically, so these should no longer be reported as an error.

300 – Multiple Choices
301 – Moved permanently
302 – Moved temporarily
303 – See other
304 – Not modified
305 – Use proxy
307 – Temporary Redirect

4?? errors

Errors with a code in the range 400-499 occur where the Web server – incorrectly or not – dislikes the HTTP data streams that the client sends to it. Quite rare.

400 – Bad request
401 – Unauthorized
403 – Forbidden
404 – Not found
405 – Method not allowed
406 – Not acceptable
407 – Proxy authentication required
408 – Request timeout
409 – Conflict
410 – Gone
411 – Length required
412 – Precondition failed
413 – Request entity too large
414 – Request URI too long
415 – Unsupported media type
416 – Requested Range not satisfiable
417 – Expectation failed

5?? errors

Errors with a code in the range 500-599 occur where the Web server reports an internal error in its operations.

500 – Internal server error
501 – Not implemented
502 – Bad gateway
503 – Service unavailable
504 – Gateway timeout
505 – HTTP version not supported

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请联系我们举报,一经查实,本站将立刻删除。

发布者:全栈程序员-站长,转载请注明出处:https://javaforall.net/100480.html原文链接:https://javaforall.net

(0)
全栈程序员-站长的头像全栈程序员-站长


相关推荐

  • tensorflow2.0手写数字识别_tensorflow手写数字识别

    tensorflow2.0手写数字识别_tensorflow手写数字识别本节笔记作为Tensorflow的HelloWorld,用MNIST手写数字识别来探索Tensorflow。笔记的内容来自Tensorflow中文社区和黄文坚的《Tensorflow实战》,只作为自己复习总结。

    2025年11月17日
    4
  • 浅析ASP.NET的IIS映射

    浅析ASP.NET的IIS映射

    2021年8月6日
    71
  • 数据库系统的特点_关系数据模型只能表示

    数据库系统的特点_关系数据模型只能表示数据结构化:数据库系统实现整体数据的结构化,是数据库的主要特征之一,也是数据库系统与文件系统的本质区别。“整体”结构化是指在数据库中的数据不再仅仅针对某一应用,而是面向全组织,不仅数据内部结构化,

    2022年8月2日
    8
  • 数据库四大特性及数据库隔离级别

    数据库四大特性及数据库隔离级别MySql本篇文章主要介绍数据库的四大特性ACID,以及说明一下数据库的隔离级别。如果想要说明一个数据库或者一个框架支持事务性操作,则必须要满足下面的四大特性1.原子性(Atomicity)原子性是指事务包含的所有操作要么全部成功,要么全部失败回滚。失败回滚的操作事务,将不能对事物有任何影响。2.一致性(Consistency)一致性是指事务必须使数据库从一个一致性状态变换到另一个一致性状态,…

    2022年5月26日
    38
  • 企业级PHP发卡网源码,金发卡企业级发卡平台源码

    企业级PHP发卡网源码,金发卡企业级发卡平台源码【实例简介】PHP环境:php5.XMySQL环境:mysql5.6服务器需开启伪静态后台默认账号密码:账号:admin密码:admin123配置说明:数据恢复文件目录\a8tgconfig\180626145246.sql或者通过客户端直接还原Back.psc数据库配置文件:\a8tgconfig\config.php修改相关数据库IP,账号,密码支付接口相关…

    2022年7月14日
    19
  • ssdp java_SSDP协议 – 实施[通俗易懂]

    ssdp java_SSDP协议 – 实施[通俗易懂]我正在尝试实现SSDP协议,但我不确定它是如何工作的.SSDP通过udp发送数据,这很清楚.如果控制器连接到网络,它可以搜索具有MSEARCH消息的设备,该消息可以发送到多播地址239.255.255.250:1900.每个设备都必须收听此地址并做出响应.但我不知道他们是如何回应的.我在wireshark中看到他们用单播响应,但我不知道如何确定接收响应的端口.编辑–…

    2022年10月11日
    4

发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

关注全栈程序员社区公众号