List of HTTP header fields (English Wikipedia)
Analysis of information sources in references of the Wikipedia article "List of HTTP header fields" in English language version.
refsWebsite
Global rank
English rank
6,184th place
4,465th place
1,686th place
1,293rd place
1st place
1st place
153rd place
151st place
low place
low place
4,643rd place
2,973rd place
8,307th place
5,922nd place
1,010th place
612th place
low place
low place
low place
low place
3,206th place
2,477th place
low place
low place
low place
low place
low place
low place
low place
low place
34th place
27th place
low place
low place
low place
low place
low place
low place
low place
low place
low place
low place
low place
low place
1,091st place
936th place
low place
low place
383rd place
320th place
4,942nd place
4,061st place
low place
low place
amifloced.org (Global: low place; English: low place)
- "Am I FLoCed?". EFF. 2021. Retrieved May 1, 2021.
angularjs.org (Global: low place; English: low place)
docs.angularjs.org
- "Angular Cross Site Request Forgery (XSRF) Protection". AngularJS. Retrieved January 20, 2015.
apache.org (Global: 3,206th place; English: 2,477th place)
httpd.apache.org
- The Apache Software Foundation. "mod_proxy - Apache HTTP Server Version 2.2". Retrieved November 12, 2014.
att.com (Global: 6,123rd place; English: 4,716th place)
developer.att.com
- "ATT Device ID". Archived from the original on February 16, 2012. Retrieved January 14, 2012.
code.google.com (Global: 4,942nd place; English: 4,061st place)
- "Hosting - Google Chrome Extensions - Google Code". Retrieved June 14, 2012.
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.
developershome.com (Global: low place; English: low place)
- "WAP Profile". Retrieved January 14, 2012.
djangoproject.com (Global: low place; English: low place)
docs.djangoproject.com
- "Django Cross Site Request Forgery protection". Django (web framework). Archived from the original on January 20, 2015. Retrieved January 20, 2015.
doi.org (Global: 2nd place; English: 2nd place)
- Saint-Andre, P.; Crocker, D.; Nottingham, M. (June 1, 2012). Deprecating the "X-" Prefix and Similar Constructs in Application Protocols. doi:10.17487/RFC6648. RFC 6648.
- "Comments". HTTP Semantics. June 2022. sec. 5.6.5. doi:10.17487/RFC9110. RFC 9110.
- "Quality Values". HTTP Semantics. June 2022. sec. 12.4.2. doi:10.17487/RFC9110. RFC 9110.
- RFC 3229. doi:10.17487/RFC3229.
- "Pragme". HTTP Caching. June 2022. sec. 5.4. doi:10.17487/RFC9111. RFC 9111.
- "Connection header". HTTP Semantics. June 2022. sec. 7.6.1. doi:10.17487/RFC9110. RFC 9110.
- "Connection-Specific Header Fields". HTTP/2. June 2022. sec. 8.2.2. doi:10.17487/RFC9113. RFC 9113.
- "Changes from RFC 2616". Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content. June 2014. sec. B. doi:10.17487/RFC7231. RFC 7231.
- Petersson, A.; Nilsson, M. (June 2014). Forwarded HTTP Extension: Introduction. IETF. doi:10.17487/RFC7239. RFC 7239.
- "Host and :authority". HTTP Semantics. June 2022. sec. 7.2. doi:10.17487/RFC9110. RFC 9110.
- "Request Pseudo-Header Fields". HTTP/2. June 2022. sec. 8.3.1. doi:10.17487/RFC9113. RFC 9113.
- "HTTP2-Settings Header Field". Hypertext Transfer Protocol Version 2 (HTTP/2). sec. 3.2.1. doi:10.17487/RFC7540. RFC 7540.
- "Warning header". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
- "Warning". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
- 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.
- Dusseault, L.; Snell, J. (2010). PATCH Method for HTTP. doi:10.17487/RFC5789. RFC 5789.
- Nottingham, M.; McManus, P.; Reschke, J. (April 2016). HTTP Alternative Services, section 3. IETF. doi:10.17487/RFC7838. RFC 7838.
- Reschke, J. (2011). Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP). doi:10.17487/RFC6266. RFC 6266.
- "Content-Language". HTTP Semantics. June 2022. sec. 8.5. doi:10.17487/RFC9110. RFC 9110.
- "Retry-After". HTTP Semantics. June 2022. sec. 10.2.3. doi:10.17487/RFC9110. RFC 9110.
eff.org (Global: 3,285th place; English: 2,156th place)
- "Verizon Injecting Perma-Cookies to Track Mobile Customers, Bypassing Privacy Controls". Electronic Frontier Foundation. Retrieved January 19, 2014.
geekisp.com (Global: low place; English: low place)
- Dave Steinberg (April 10, 2007). "How do I adjust my SSL site to work with GeekISP's loadbalancer?". Retrieved September 30, 2010.
github.com (Global: 383rd place; English: 320th place)
- "Define the HTTP Refresh header by annevk · Pull Request #2892 · whatwg/html". GitHub. August 9, 2017. Retrieved April 17, 2021.
heroku.com (Global: low place; English: low place)
devcenter.heroku.com
- "HTTP Request IDs". devcenter.heroku.com. Retrieved March 22, 2022.
hilton.org.uk (Global: low place; English: low place)
- Hilton, Peter (July 12, 2017). "Correlation IDs for microservices architectures - Peter Hilton". hilton.org.uk. Retrieved April 13, 2018.
iana.org (Global: 1,884th place; English: 1,694th place)
- "Message Headers". Iana.org. June 11, 2014. Retrieved June 12, 2014.
- "Message Headers". www.iana.org. Retrieved November 26, 2018.
ietf.org (Global: 214th place; English: 176th place)
datatracker.ietf.org
- Saint-Andre, P.; Crocker, D.; Nottingham, M. (June 1, 2012). Deprecating the "X-" Prefix and Similar Constructs in Application Protocols. doi:10.17487/RFC6648. RFC 6648.
- "Comments". HTTP Semantics. June 2022. sec. 5.6.5. doi:10.17487/RFC9110. RFC 9110.
- "Quality Values". HTTP Semantics. June 2022. sec. 12.4.2. doi:10.17487/RFC9110. RFC 9110.
- "Pragme". HTTP Caching. June 2022. sec. 5.4. doi:10.17487/RFC9111. RFC 9111.
- "Connection header". HTTP Semantics. June 2022. sec. 7.6.1. doi:10.17487/RFC9110. RFC 9110.
- "Connection-Specific Header Fields". HTTP/2. June 2022. sec. 8.2.2. doi:10.17487/RFC9113. RFC 9113.
- "Changes from RFC 2616". Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content. June 2014. sec. B. doi:10.17487/RFC7231. RFC 7231.
- Petersson, A.; Nilsson, M. (June 2014). Forwarded HTTP Extension: Introduction. IETF. doi:10.17487/RFC7239. RFC 7239.
- "Host and :authority". HTTP Semantics. June 2022. sec. 7.2. doi:10.17487/RFC9110. RFC 9110.
- "Request Pseudo-Header Fields". HTTP/2. June 2022. sec. 8.3.1. doi:10.17487/RFC9113. RFC 9113.
- "HTTP2-Settings Header Field". Hypertext Transfer Protocol Version 2 (HTTP/2). sec. 3.2.1. doi:10.17487/RFC7540. RFC 7540.
- "Warning header". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
- "Warning". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
- 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.
- Dusseault, L.; Snell, J. (2010). PATCH Method for HTTP. doi:10.17487/RFC5789. RFC 5789.
- Nottingham, M.; McManus, P.; Reschke, J. (April 2016). HTTP Alternative Services, section 3. IETF. doi:10.17487/RFC7838. RFC 7838.
- Reschke, J. (2011). Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP). doi:10.17487/RFC6266. RFC 6266.
- "Content-Language". HTTP Semantics. June 2022. sec. 8.5. doi:10.17487/RFC9110. RFC 9110.
- "Retry-After". HTTP Semantics. June 2022. sec. 10.2.3. doi:10.17487/RFC9110. RFC 9110.
tools.ietf.org
- Petersson, A.; Nilsson, M. (June 2014). Forwarded HTTP Extension: Introduction. IETF. doi:10.17487/RFC7239. RFC 7239.
- IETF Do Not Track: A Universal Third-Party Web Tracking Opt Out March 7, 2011
- Dusseault, L.; Snell, J. (2010). PATCH Method for HTTP. doi:10.17487/RFC5789. RFC 5789.
- Nottingham, M.; McManus, P.; Reschke, J. (April 2016). HTTP Alternative Services, section 3. IETF. doi:10.17487/RFC7838. RFC 7838.
jdebp.eu (Global: low place; English: low place)
- de Boyne Pollard, Jonathan (2007). "The Proxy-Connection: header is a mistake in how some web browsers use HTTP". Archived from the original on October 23, 2016. Retrieved January 16, 2018.
lessonslearned.org (Global: low place; English: low place)
- "Checking known AT&T, Verizon, Sprint, Bell Canada & Vodacom Unique Identifier beacons". Retrieved January 19, 2014.
microsoft.com (Global: 153rd place; English: 151st place)
support.microsoft.com
- "How to prevent caching in Internet Explorer". Microsoft. September 22, 2011. Retrieved April 15, 2015.
technet.microsoft.com
- "Helping to Secure Communication: Client to Front-End Server". July 27, 2006. Retrieved April 23, 2012.
msdn.microsoft.com
- "Defining Document Compatibility: Specifying Document Compatibility Modes". April 1, 2011. Retrieved January 24, 2012.
mozilla.org (Global: 1,686th place; English: 1,293rd place)
developer.mozilla.org
- "Warning – HTTP | MDN". developer.mozilla.org. Retrieved August 15, 2021. This article incorporates text available under the CC BY-SA 2.5 license.
- MDN contributors (March 3, 2023). "Sec-GPC". MDN Web Docs. Retrieved March 12, 2023.
- "Expect-CT". Mozilla Developer Network. Retrieved July 23, 2021.
- "NEL". Mozilla Developer Network. 2021. Retrieved May 18, 2021.
- "CSP: report-to". Mozilla Developer Network. 2021. Retrieved May 18, 2021.
- "Timing-Allow-Origin". Mozilla Developer Network. Retrieved January 25, 2018.
- "Configuring servers for Ogg media". May 26, 2014. Retrieved January 3, 2015.
bugzilla.mozilla.org
- "Clean up duration tracking and use mirroring for cross-thread access". Bugzilla@Mozilla. Retrieved February 9, 2024.
msdn.com (Global: 3,029th place; English: 2,272nd place)
blogs.msdn.com
- Eric Lawrence (September 3, 2008). "IE8 Security Part VI: Beta 2 Update". Retrieved September 28, 2010.
- Eric Lawrence (July 2, 2008). "IE8 Security Part IV: The XSS Filter". Retrieved September 30, 2010.
opensocial.github.io (Global: low place; English: low place)
- "OpenSocial Core API Server Specification 2.5.1". Retrieved October 8, 2014.
rapid7.com (Global: low place; English: low place)
blog.rapid7.com
- "The Value of Correlation IDs". Rapid7 Blog. December 23, 2016. Retrieved April 13, 2018.
rfc-editor.org (Global: 6,184th place; English: 4,465th place)
- Saint-Andre, P.; Crocker, D.; Nottingham, M. (June 1, 2012). Deprecating the "X-" Prefix and Similar Constructs in Application Protocols. doi:10.17487/RFC6648. RFC 6648.
- "Comments". HTTP Semantics. June 2022. sec. 5.6.5. doi:10.17487/RFC9110. RFC 9110.
- "Quality Values". HTTP Semantics. June 2022. sec. 12.4.2. doi:10.17487/RFC9110. RFC 9110.
- RFC 3229. doi:10.17487/RFC3229.
- "Pragme". HTTP Caching. June 2022. sec. 5.4. doi:10.17487/RFC9111. RFC 9111.
- "Connection header". HTTP Semantics. June 2022. sec. 7.6.1. doi:10.17487/RFC9110. RFC 9110.
- "Connection-Specific Header Fields". HTTP/2. June 2022. sec. 8.2.2. doi:10.17487/RFC9113. RFC 9113.
- "Changes from RFC 2616". Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content. June 2014. sec. B. doi:10.17487/RFC7231. RFC 7231.
- "Host and :authority". HTTP Semantics. June 2022. sec. 7.2. doi:10.17487/RFC9110. RFC 9110.
- "Request Pseudo-Header Fields". HTTP/2. June 2022. sec. 8.3.1. doi:10.17487/RFC9113. RFC 9113.
- "HTTP2-Settings Header Field". Hypertext Transfer Protocol Version 2 (HTTP/2). sec. 3.2.1. doi:10.17487/RFC7540. RFC 7540.
- "Warning header". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
- "Warning". HTTP Caching. June 2022. sec. 5.5. doi:10.17487/RFC9111. RFC 9111.
- 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.
- Reschke, J. (2011). Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP). doi:10.17487/RFC6266. RFC 6266.
- "Content-Language". HTTP Semantics. June 2022. sec. 8.5. doi:10.17487/RFC9110. RFC 9110.
- "Public Key Pinning Extension for HTTP". IETF. Retrieved April 17, 2015.
- "Retry-After". HTTP Semantics. June 2022. sec. 10.2.3. doi:10.17487/RFC9110. RFC 9110.
- RFC 9110: HTTP Semantics
sap.com (Global: 6,117th place; English: 4,815th place)
help.sap.com
- "SAP Cross-Site Request Forgery Protection". SAP SE. Retrieved January 20, 2015.
sidstamm.com (Global: low place; English: low place)
blog.sidstamm.com
- "Try out the "Do Not Track" HTTP header". Retrieved January 31, 2011.
- "Do Not Track field reference from col 1".
squid-cache.org (Global: low place; English: low place)
wiki.squid-cache.org
- Amos Jeffries (July 2, 2010). "SquidFaq/ConfiguringSquid - Squid Web Proxy Wiki". Retrieved September 10, 2009.
stackoverflow.com (Global: 4,643rd place; English: 2,973rd place)
- "What is the X-REQUEST-ID http header?". Retrieved March 20, 2022.
- "Why does ASP.NET framework add the 'X-Powered-By:ASP.NET' HTTP Header in responses? - Stack Overflow". Retrieved March 20, 2022.
stoutner.com (Global: low place; English: low place)
- "The "X-Requested-With" Header – Stoutner". October 31, 2022.
support.google.com (Global: 1,091st place; English: 936th place)
w3.org (Global: 691st place; English: 581st place)
- "Cross-Origin Resource Sharing". Retrieved July 24, 2017.
- "Upgrade Insecure Requests - W3C Candidate Recommendation". W3C. October 8, 2015. Retrieved January 14, 2016.
- W3C Tracking Preference Expression (DNT), January 26, 2012
- "W3C Trace Context". w3c.org. Retrieved June 19, 2024.
- W3C P3P Work Suspended
- "Content Security Policy Level 2". Retrieved August 2, 2014.
- "Content Security Policy". W3C. 2012. Retrieved April 28, 2017.
- "Permissions Policy". W3C. 2020. Retrieved May 1, 2021.
washingtonpost.com (Global: 34th place; English: 27th place)
- Craig Timberg. "Verizon, AT&T tracking their users with 'supercookies'". The Washington Post. Retrieved January 19, 2014.
web.archive.org (Global: 1st place; English: 1st place)
- "ATT Device ID". Archived from the original on February 16, 2012. Retrieved January 14, 2012.
- de Boyne Pollard, Jonathan (2007). "The Proxy-Connection: header is a mistake in how some web browsers use HTTP". Archived from the original on October 23, 2016. Retrieved January 16, 2018.
- "Django Cross Site Request Forgery protection". Django (web framework). Archived from the original on January 20, 2015. Retrieved January 20, 2015.
- van Kesteren, Anne (August 26, 2016). "Fetch standard". WHATWG. Archived from the original on August 26, 2016. Retrieved August 26, 2016.
webtechsurvey.com (Global: low place; English: low place)
- "X-Redirect-By HTTP response header". Retrieved May 29, 2021.
whatwg.org (Global: 8,307th place; English: 5,922nd place)
fetch.spec.whatwg.org
- van Kesteren, Anne (August 26, 2016). "Fetch standard". WHATWG. Archived from the original on August 26, 2016. Retrieved August 26, 2016.
html.spec.whatwg.org
- "HTML Living Standard 4.2.5.3 Pragma directives, X-UA-Compatible state". WHATWG. March 12, 2021. Retrieved March 14, 2021.
For meta elements with an http-equiv attribute in the X-UA-Compatible state, the content attribute must have a value that is an ASCII case-insensitive match for the string
"IE=edge".
wicg.github.io (Global: low place; English: low place)
- "Save Data API Living Document Draft Community Group Report 2.1.1. Save-Data Request Header Field". Web Platform Incubator Community Group. June 30, 2020. Retrieved March 5, 2021.