List of HTTP status codes (English Wikipedia)
Analysis of information sources in references of the Wikipedia article "List of HTTP status codes" in English language version.
refsWebsite
Global rank
English rank
1st place
1st place
6,184th place
4,465th place
8,991st place
6,535th place
153rd place
151st place
1,686th place
1,293rd place
5th place
5th place
4,643rd place
2,973rd place
163rd place
185th place
383rd place
320th place
low place
low place
2,697th place
3,971st place
low place
low place
low place
low place
low place
low place
low place
low place
7,076th place
4,822nd place
low place
low place
1,317th place
873rd place
23rd place
32nd place
low place
low place
low place
low place
low place
low place
2,359th place
1,698th place
low place
low place
low place
low place
14th place
14th place
105th place
79th place
1,010th place
612th place
amazon.com (Global: 105th place; English: 79th place)
docs.aws.amazon.com
- "Troubleshoot Your Application Load Balancers – Elastic Load Balancing". docs.aws.amazon.com. Retrieved May 17, 2023.
arcgis.com (Global: 2,359th place; English: 1,698th place)
help.arcgis.com
- "Using token-based authentication". ArcGIS Server SOAP SDK. Archived from the original on September 26, 2014. Retrieved September 8, 2014.
archive.today (Global: 14th place; English: 14th place)
ascii-code.com (Global: low place; English: low place)
- "HTTP status codes – ascii-code.com". www.ascii-code.com. Archived from the original on January 7, 2017. Retrieved December 23, 2016.
cloudflare.com (Global: 8,991st place; English: 6,535th place)
developers.cloudflare.com
- "Cloudflare support docs". developers.cloudflare.com. April 29, 2025. Retrieved September 14, 2025.
- "Cloudflare support docs". developers.cloudflare.com. August 11, 2025. Retrieved September 14, 2025.
- "Cloudflare support docs". developers.cloudflare.com. April 29, 2025. Retrieved September 14, 2025.
- "Error 520: web server returns an unknown error". Cloudflare. May 29, 2025.
- "Error 521: web server is down". Cloudflare. April 29, 2025.
- "Error 522: connection timed out". Cloudflare. May 5, 2025.
- "Error 523: origin is unreachable". Cloudflare. April 29, 2025.
- "Error 524: a timeout occurred". Cloudflare. August 6, 2025.
- "Error 525: SSL handshake failed". Cloudflare. April 29, 2025.
- "Error 526: invalid SSL certificate". Cloudflare. August 11, 2025.
- "527 Error: Railgun Listener to origin error". Cloudflare. Archived from the original on October 13, 2016. Retrieved October 12, 2016.
- "Error 530". Cloudflare. Retrieved November 1, 2019.
support.cloudflare.com
- "Troubleshooting: Error Pages". Cloudflare. Archived from the original on March 4, 2016. Retrieved January 9, 2016.
contentkingapp.com (Global: low place; English: low place)
- "HTTP Status Codes and SEO: what you need to know". ContentKing. Retrieved August 9, 2019.
cpanel.net (Global: low place; English: low place)
support.cpanel.net
- "Receiving a "508 Resource Limit Is Reached" error when browsing a site on CloudLinux". September 28, 2021. Archived from the original on July 19, 2025. Retrieved July 19, 2025.
documentation.cpanel.net
- "HTTP Error Codes and Quick Fixes". Docs.cpanel.net. Archived from the original on November 23, 2015. Retrieved October 15, 2015.
creativecommons.org (Global: 1,010th place; English: 612th place)
- "Warning – HTTP | MDN". developer.mozilla.org. Retrieved August 15, 2021.
This article incorporates text available under the CC BY-SA 2.5 license.
developers.google.com (Global: 2,697th place; English: 3,971st place)
- "Google API Standard Error Responses". 2016. Archived from the original on May 25, 2017. Retrieved June 21, 2017.
doi.org (Global: 2nd place; English: 2nd place)
- R. Fielding; M. Nottingham; J. Reschke, eds. (June 2022). HTTP Semantics. Internet Engineering Task Force. doi:10.17487/RFC9110. ISSN 2070-1721. STD 97. RFC 9110. Internet Standard 97. Obsoletes RFC 2818, 7230, 7231, 7232, 7233, 7235, 7538, 7615 and 7694. Updates RFC 3864.
- Goland, Yaronn; Whitehead, Jim; Faizi, Asad; Carter, Steve R.; Jensen, Del (February 1999). HTTP Extensions for Distributed Authoring – WEBDAV. Network Working Group. doi:10.17487/RFC2518. RFC 2518. Proposed Standard. Obsoleted by RFC 4918.
- Oku, Kazuho (December 2017). An HTTP Status Code for Indicating Hints. Internet Engineering Task Force. doi:10.17487/RFC8297. RFC 8297. Experimental.
- Dusseault, Lisa, ed. (June 2007). HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV). Network Working Group. doi:10.17487/RFC4918. RFC 4918. Proposed Standard. Updated by RFC 5689. Obsoletes RFC 2518.
- Hoff, Arthur van; Douglis, Fred; Krishnamurthy, Balachander; Goland, Yaron Y.; Hellerstein, Daniel M.; Feldmann, Anja; Mogul, Jeffrey (January 2002). Delta encoding in HTTP. Network Working Group. doi:10.17487/RFC3229. RFC 3229. Proposed Standard.
- T Berners-Lee; R. Fielding; H. Frystyk (May 1996). Hypertext Transfer Protocol -- HTTP/1.0. Network Working Group. doi:10.17487/RFC1945. RFC 1945. Informational.
- R. Fielding; J. Gettys; J. Mogul; H. Frystyk; L. Masinter; P. Leach; T. Berners-Lee (August 1999). Hypertext Transfer Protocol -- HTTP/1.1. Network Working Group. doi:10.17487/RFC2616. RFC 2616. Obsolete. Obsoleted by RFC 7230, 7231, 7232, 7233, 7234 and 7235. Obsoletes RFC 2068. Updated by RFC 2817, 5785, 6266 and 6585.
- L. Masinter (April 1, 1998). Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). Network Working Group. doi:10.17487/RFC2324. RFC 2324. Informational. Updated by RFC 7168. This is an April Fools' Day Request for Comments.
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.
- M. Nottingham; R. Fielding (April 2012). Additional HTTP Status Codes. Internet Engineering Task Force. doi:10.17487/RFC6585. ISSN 2070-1721. RFC 6585. Proposed Standard. Updates RFC 2616.
- K. Holtman; A.H. Mutz (March 1998). Transparent Content Negotiation in HTTP. Network Working Group. doi:10.17487/RFC2295. RFC 2295. Experimental.
- Nielsen, Henrik Frystyk; Leach, Paul; Lawrence, Scott (February 2000). An HTTP Extension Framework. Network Working Group. doi:10.17487/RFC2774. RFC 2774. Historic.
- R. Fielding; M. Nottingham; J. Reschke (June 2014). Hypertext Transfer Protocol (HTTP/1.1): Caching. Internet Engineering Task Force. doi:10.17487/RFC7234. RFC 7234. Obsolete. sec. 5.5. Obsoleted by RFC 9111. Obsoletes RFC 2616.
- "Warning". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
dreamhost.com (Global: low place; English: low place)
help.dreamhost.com
- "Enable extra web security on a website". DreamHost. Retrieved December 18, 2022.
github.com (Global: 383rd place; English: 320th place)
- "framework/src/Illuminate/Foundation/Exceptions/Handler.php". GitHub. Retrieved December 12, 2023.
- "SSL Labs API v3 Documentation". github.com.
google.com (Global: 163rd place; English: 185th place)
- I'm a teapot
- "Google's Teapot". Retrieved October 23, 2017.
http.dev (Global: low place; English: low place)
- "218 This is fine – HTTP status code explained". HTTP.dev. Retrieved July 25, 2023.
iana.org (Global: 1,884th place; English: 1,694th place)
- "Hypertext Transfer Protocol (HTTP) Status Code Registry". Iana.org. Archived from the original on December 11, 2011. Retrieved January 8, 2015.
ietf.org (Global: 214th place; English: 176th place)
datatracker.ietf.org
- R. Fielding; M. Nottingham; J. Reschke, eds. (June 2022). HTTP Semantics. Internet Engineering Task Force. doi:10.17487/RFC9110. ISSN 2070-1721. STD 97. RFC 9110. Internet Standard 97. Obsoletes RFC 2818, 7230, 7231, 7232, 7233, 7235, 7538, 7615 and 7694. Updates RFC 3864.
- Goland, Yaronn; Whitehead, Jim; Faizi, Asad; Carter, Steve R.; Jensen, Del (February 1999). HTTP Extensions for Distributed Authoring – WEBDAV. Network Working Group. doi:10.17487/RFC2518. RFC 2518. Proposed Standard. Obsoleted by RFC 4918.
- Oku, Kazuho (December 2017). An HTTP Status Code for Indicating Hints. Internet Engineering Task Force. doi:10.17487/RFC8297. RFC 8297. Experimental.
- Dusseault, Lisa, ed. (June 2007). HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV). Network Working Group. doi:10.17487/RFC4918. RFC 4918. Proposed Standard. Updated by RFC 5689. Obsoletes RFC 2518.
- Hoff, Arthur van; Douglis, Fred; Krishnamurthy, Balachander; Goland, Yaron Y.; Hellerstein, Daniel M.; Feldmann, Anja; Mogul, Jeffrey (January 2002). Delta encoding in HTTP. Network Working Group. doi:10.17487/RFC3229. RFC 3229. Proposed Standard.
- T Berners-Lee; R. Fielding; H. Frystyk (May 1996). Hypertext Transfer Protocol -- HTTP/1.0. Network Working Group. doi:10.17487/RFC1945. RFC 1945. Informational.
- R. Fielding; J. Gettys; J. Mogul; H. Frystyk; L. Masinter; P. Leach; T. Berners-Lee (August 1999). Hypertext Transfer Protocol -- HTTP/1.1. Network Working Group. doi:10.17487/RFC2616. RFC 2616. Obsolete. Obsoleted by RFC 7230, 7231, 7232, 7233, 7234 and 7235. Obsoletes RFC 2068. Updated by RFC 2817, 5785, 6266 and 6585.
- L. Masinter (April 1, 1998). Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). Network Working Group. doi:10.17487/RFC2324. RFC 2324. Informational. Updated by RFC 7168. This is an April Fools' Day Request for Comments.
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.
- M. Nottingham; R. Fielding (April 2012). Additional HTTP Status Codes. Internet Engineering Task Force. doi:10.17487/RFC6585. ISSN 2070-1721. RFC 6585. Proposed Standard. Updates RFC 2616.
- K. Holtman; A.H. Mutz (March 1998). Transparent Content Negotiation in HTTP. Network Working Group. doi:10.17487/RFC2295. RFC 2295. Experimental.
- Nielsen, Henrik Frystyk; Leach, Paul; Lawrence, Scott (February 2000). An HTTP Extension Framework. Network Working Group. doi:10.17487/RFC2774. RFC 2774. Historic.
- "draft-ietf-webdav-protocol-05: Extensions for Distributed Authoring on the World Wide Web -- WEBDAV".
- R. Fielding; M. Nottingham; J. Reschke (June 2014). Hypertext Transfer Protocol (HTTP/1.1): Caching. Internet Engineering Task Force. doi:10.17487/RFC7234. RFC 7234. Obsolete. sec. 5.5. Obsoleted by RFC 9111. Obsoletes RFC 2616.
- "Warning". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
tools.ietf.org
- Bray, T. (February 2016). "An HTTP Status Code to Report Legal Obstacles". ietf.org. Archived from the original on March 4, 2016. Retrieved March 7, 2015.
livefilestore.com (Global: low place; English: low place)
public.bn1.livefilestore.com
- "Screenshot of error page". Archived from the original (bmp) on May 11, 2013. Retrieved October 11, 2009.
microsoft.com (Global: 153rd place; English: 151st place)
msdn.microsoft.com
- "2.2.6 449 Retry With Status Code". Microsoft. 2009. Archived from the original on October 5, 2009. Retrieved October 26, 2009.
- "MS-ASCMD, Section 3.1.5.2.2". Msdn.microsoft.com. Archived from the original on March 26, 2015. Retrieved January 8, 2015.
- "Ms-oxdisco". Msdn.microsoft.com. Archived from the original on July 31, 2014. Retrieved January 8, 2015.
support.microsoft.com
- "Error message when you try to log on to Exchange 2007 by using Outlook Web Access: "440 Login Time-out"". Microsoft. 2010. Retrieved November 13, 2013.
- "The HTTP status codes in IIS 7.0". Microsoft. July 14, 2009. Archived from the original on April 9, 2009. Retrieved April 1, 2009.
learn.microsoft.com
mozilla.org (Global: 1,686th place; English: 1,293rd place)
developer.mozilla.org
- "102 Processing – HTTP MDN". July 25, 2023. 102 status code is deprecated
- "409 Conflict". MDN Web Docs. March 13, 2025. Retrieved June 11, 2025.
- "Warning – HTTP | MDN". developer.mozilla.org. Retrieved August 15, 2021. This article incorporates text available under the CC BY-SA 2.5 license.
bugzilla.mozilla.org
- "Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect, comment 13". March 3, 2003. Archived from the original on April 21, 2014. Retrieved May 21, 2009.
nginx.org (Global: low place; English: low place)
lxr.nginx.org
- "ngx_http_request.h". nginx 1.9.5 source code. nginx inc. Archived from the original on September 19, 2017. Retrieved January 9, 2016.
- "ngx_http_special_response.c". nginx 1.9.5 source code. nginx inc. Archived from the original on May 8, 2018. Retrieved January 9, 2016.
nginx.org
- "return" directive Archived March 1, 2018, at the Wayback Machine (http_rewrite module) documentation.
pantheon.io (Global: low place; English: low place)
- "Platform Considerations | Pantheon Docs". pantheon.io. Archived from the original on January 6, 2017. Retrieved January 5, 2017.
pcmag.com (Global: 1,060th place; English: 700th place)
- "I Went to a Russian Website and All I Got Was This Lousy Teapot". PCMag. February 25, 2022. Retrieved December 18, 2022.
pcworld.com (Global: 1,317th place; English: 873rd place)
- Paul, Ian (December 21, 2015). "Error 451 is the new Ray Bradbury-inspired HTTP code for online censorship". PC World. Retrieved July 18, 2025.
rfc-editor.org (Global: 6,184th place; English: 4,465th place)
- Emphasised words and phrases such as must and should represent interpretation guidelines as given by RFC 2119
- R. Fielding; M. Nottingham; J. Reschke, eds. (June 2022). HTTP Semantics. Internet Engineering Task Force. doi:10.17487/RFC9110. ISSN 2070-1721. STD 97. RFC 9110. Internet Standard 97. Obsoletes RFC 2818, 7230, 7231, 7232, 7233, 7235, 7538, 7615 and 7694. Updates RFC 3864.
- Goland, Yaronn; Whitehead, Jim; Faizi, Asad; Carter, Steve R.; Jensen, Del (February 1999). HTTP Extensions for Distributed Authoring – WEBDAV. Network Working Group. doi:10.17487/RFC2518. RFC 2518. Proposed Standard. Obsoleted by RFC 4918.
- Oku, Kazuho (December 2017). An HTTP Status Code for Indicating Hints. Internet Engineering Task Force. doi:10.17487/RFC8297. RFC 8297. Experimental.
- Dusseault, Lisa, ed. (June 2007). HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV). Network Working Group. doi:10.17487/RFC4918. RFC 4918. Proposed Standard. Updated by RFC 5689. Obsoletes RFC 2518.
- Hoff, Arthur van; Douglis, Fred; Krishnamurthy, Balachander; Goland, Yaron Y.; Hellerstein, Daniel M.; Feldmann, Anja; Mogul, Jeffrey (January 2002). Delta encoding in HTTP. Network Working Group. doi:10.17487/RFC3229. RFC 3229. Proposed Standard.
- T Berners-Lee; R. Fielding; H. Frystyk (May 1996). Hypertext Transfer Protocol -- HTTP/1.0. Network Working Group. doi:10.17487/RFC1945. RFC 1945. Informational.
- R. Fielding; J. Gettys; J. Mogul; H. Frystyk; L. Masinter; P. Leach; T. Berners-Lee (August 1999). Hypertext Transfer Protocol -- HTTP/1.1. Network Working Group. doi:10.17487/RFC2616. RFC 2616. Obsolete. Obsoleted by RFC 7230, 7231, 7232, 7233, 7234 and 7235. Obsoletes RFC 2068. Updated by RFC 2817, 5785, 6266 and 6585.
- L. Masinter (April 1, 1998). Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). Network Working Group. doi:10.17487/RFC2324. RFC 2324. Informational. Updated by RFC 7168. This is an April Fools' Day Request for Comments.
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.
- M. Nottingham; R. Fielding (April 2012). Additional HTTP Status Codes. Internet Engineering Task Force. doi:10.17487/RFC6585. ISSN 2070-1721. RFC 6585. Proposed Standard. Updates RFC 2616.
- K. Holtman; A.H. Mutz (March 1998). Transparent Content Negotiation in HTTP. Network Working Group. doi:10.17487/RFC2295. RFC 2295. Experimental.
- Nielsen, Henrik Frystyk; Leach, Paul; Lawrence, Scott (February 2000). An HTTP Extension Framework. Network Working Group. doi:10.17487/RFC2774. RFC 2774. Historic.
- R. Fielding; M. Nottingham; J. Reschke (June 2014). Hypertext Transfer Protocol (HTTP/1.1): Caching. Internet Engineering Task Force. doi:10.17487/RFC7234. RFC 7234. Obsolete. sec. 5.5. Obsoleted by RFC 9111. Obsoletes RFC 2616.
- "Warning". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
searchengineland.com (Global: 7,076th place; English: 4,822nd place)
- Barry Schwartz (August 26, 2014). "New Google Easter Egg For SEO Geeks: Server Status 418, I'm A Teapot". Search Engine Land. Archived from the original on November 15, 2015. Retrieved November 4, 2015.
serverfault.com (Global: low place; English: low place)
- TheDeadLike. "HTTP/1.1 Status Codes 400 and 417, cannot choose which". serverFault. Archived from the original on October 10, 2015. Retrieved October 16, 2015.
shopify.com (Global: low place; English: low place)
help.shopify.com
- "Shopify Documentation". Archived from the original on July 25, 2018. Retrieved July 25, 2018.
shopify.dev (Global: low place; English: low place)
- "Shopify API response status and error codes". Retrieved December 12, 2023.
sipgate.com (Global: low place; English: low place)
api.sipgate.com
- "Sipgate API Documentation". Archived from the original on July 10, 2018. Retrieved July 10, 2018.
spring.io (Global: low place; English: low place)
docs.spring.io
- "Enum HttpStatus". Spring Framework. org.springframework.http. Archived from the original on October 25, 2015. Retrieved October 16, 2015.
stackoverflow.com (Global: 4,643rd place; English: 2,973rd place)
- Stewart, Mark; djna. "Create request with POST, which response codes 200 or 201 and content". Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
- alex. "What is the correct HTTP status code to send when a site is down for maintenance?". Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
stripe.com (Global: low place; English: low place)
- "Stripe API Reference – Errors". stripe.com. Retrieved October 28, 2019.
taler.net (Global: low place; English: low place)
docs.taler.net
- "The GNU Taler tutorial for PHP Web shop developers 0.4.0". docs.taler.net. Archived from the original on November 8, 2017. Retrieved October 29, 2017.
twitter.com (Global: 23rd place; English: 32nd place)
developer.twitter.com
- "Twitter Error Codes & Responses". Twitter. 2014. Archived from the original on September 27, 2017. Retrieved January 20, 2014.
web.archive.org (Global: 1st place; English: 1st place)
- "Hypertext Transfer Protocol (HTTP) Status Code Registry". Iana.org. Archived from the original on December 11, 2011. Retrieved January 8, 2015.
- Stewart, Mark; djna. "Create request with POST, which response codes 200 or 201 and content". Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
- "Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect, comment 13". March 3, 2003. Archived from the original on April 21, 2014. Retrieved May 21, 2009.
- "The GNU Taler tutorial for PHP Web shop developers 0.4.0". docs.taler.net. Archived from the original on November 8, 2017. Retrieved October 29, 2017.
- "Google API Standard Error Responses". 2016. Archived from the original on May 25, 2017. Retrieved June 21, 2017.
- "Sipgate API Documentation". Archived from the original on July 10, 2018. Retrieved July 10, 2018.
- "Shopify Documentation". Archived from the original on July 25, 2018. Retrieved July 25, 2018.
- TheDeadLike. "HTTP/1.1 Status Codes 400 and 417, cannot choose which". serverFault. Archived from the original on October 10, 2015. Retrieved October 16, 2015.
- Barry Schwartz (August 26, 2014). "New Google Easter Egg For SEO Geeks: Server Status 418, I'm A Teapot". Search Engine Land. Archived from the original on November 15, 2015. Retrieved November 4, 2015.
- Bray, T. (February 2016). "An HTTP Status Code to Report Legal Obstacles". ietf.org. Archived from the original on March 4, 2016. Retrieved March 7, 2015.
- alex. "What is the correct HTTP status code to send when a site is down for maintenance?". Stack Overflow. Archived from the original on October 11, 2016. Retrieved October 16, 2015.
- "Enum HttpStatus". Spring Framework. org.springframework.http. Archived from the original on October 25, 2015. Retrieved October 16, 2015.
- "Twitter Error Codes & Responses". Twitter. 2014. Archived from the original on September 27, 2017. Retrieved January 20, 2014.
- "Screenshot of error page". Archived from the original (bmp) on May 11, 2013. Retrieved October 11, 2009.
- "Using token-based authentication". ArcGIS Server SOAP SDK. Archived from the original on September 26, 2014. Retrieved September 8, 2014.
- "Receiving a "508 Resource Limit Is Reached" error when browsing a site on CloudLinux". September 28, 2021. Archived from the original on July 19, 2025. Retrieved July 19, 2025.
- "HTTP Error Codes and Quick Fixes". Docs.cpanel.net. Archived from the original on November 23, 2015. Retrieved October 15, 2015.
- "Platform Considerations | Pantheon Docs". pantheon.io. Archived from the original on January 6, 2017. Retrieved January 5, 2017.
- "HTTP status codes – ascii-code.com". www.ascii-code.com. Archived from the original on January 7, 2017. Retrieved December 23, 2016.
- "2.2.6 449 Retry With Status Code". Microsoft. 2009. Archived from the original on October 5, 2009. Retrieved October 26, 2009.
- "MS-ASCMD, Section 3.1.5.2.2". Msdn.microsoft.com. Archived from the original on March 26, 2015. Retrieved January 8, 2015.
- "Ms-oxdisco". Msdn.microsoft.com. Archived from the original on July 31, 2014. Retrieved January 8, 2015.
- "The HTTP status codes in IIS 7.0". Microsoft. July 14, 2009. Archived from the original on April 9, 2009. Retrieved April 1, 2009.
- "ngx_http_request.h". nginx 1.9.5 source code. nginx inc. Archived from the original on September 19, 2017. Retrieved January 9, 2016.
- "ngx_http_special_response.c". nginx 1.9.5 source code. nginx inc. Archived from the original on May 8, 2018. Retrieved January 9, 2016.
- "return" directive Archived March 1, 2018, at the Wayback Machine (http_rewrite module) documentation.
- "Troubleshooting: Error Pages". Cloudflare. Archived from the original on March 4, 2016. Retrieved January 9, 2016.
- "527 Error: Railgun Listener to origin error". Cloudflare. Archived from the original on October 13, 2016. Retrieved October 12, 2016.
worldcat.org (Global: 5th place; English: 5th place)
search.worldcat.org
- R. Fielding; M. Nottingham; J. Reschke, eds. (June 2022). HTTP Semantics. Internet Engineering Task Force. doi:10.17487/RFC9110. ISSN 2070-1721. STD 97. RFC 9110. Internet Standard 97. Obsoletes RFC 2818, 7230, 7231, 7232, 7233, 7235, 7538, 7615 and 7694. Updates RFC 3864.
- M. Nottingham; R. Fielding (April 2012). Additional HTTP Status Codes. Internet Engineering Task Force. doi:10.17487/RFC6585. ISSN 2070-1721. RFC 6585. Proposed Standard. Updates RFC 2616.