歴史

[5] RFC 2068 & 2616 (HTTP/1.1) 10.4.9 408 Request Timeout

The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.

クライアントは、サーバーが待機している時間内に要求を生成しませんでした。クライアントは、後の時刻に要求を修正なしで繰り返して構いません。

[1] Issue 377581 - chromium - Chromium does not handle 408 responses - An open-source project to help move the web forward. - Google Project Hosting ( (2014-07-10 07:11:13 +09:00 版)) https://code.google.com/p/chromium/issues/detail?id=377581
[2] HAProxy and HTTP errors 408 in Chrome | HAProxy Technologies – Aloha Load Balancer ( (2014-07-10 07:11:56 +09:00 版)) http://blog.haproxy.com/2014/05/26/haproxy-and-http-errors-408-in-chrome/
[3] chromium chromium/src/net/http/http_network_transaction.cc ( (2014-07-14 05:04:37 +09:00 版)) http://mxr.mozilla.org/chromium/source/src/net/http/http_network_transaction.cc#1003

[412] RFC 3507 - Internet Content Adaptation Protocol (ICAP) ( (2014-06-08 07:17:07 +09:00 版)) http://tools.ietf.org/html/rfc3507#section-4.3.3

[7] errors: change timeout errors from 408 to 500 HTTP status code (andreastt著, 2018-08-21 18:40:30 +09:00) https://github.com/w3c/webdriver/commit/c377c21186f672105a05383d5152e0a3b2a00374

[8] HTTP status code 408 causes clients to retry · Issue #1287 · w3c/webdriver (2018-09-29 17:22:59 +09:00) https://github.com/w3c/webdriver/issues/1287

[9] errors: change timeout errors from 408 to 500 HTTP status code by andreastt · Pull Request #1292 · w3c/webdriver (2018-09-29 17:24:08 +09:00) https://github.com/w3c/webdriver/pull/1292

仕様書

意味

構文

処理モデル

歴史