List of HTTP header fields

This article lists standard and notable non-standard HTTP header fields. A core set of fields is standardized by the Internet Engineering Task Force (IETF) in RFC 9110 and 9111. The Field Names, Header Fields and Repository of Provisional Registrations are maintained by the IANA. Additional fields may be defined by a web application. In the past, non-standard header field names were prefixed with X- but this convention was deprecated in June 2012 because of the inconveniences it caused when non-standard fields became standard. An earlier restriction on use of Downgraded- was lifted in March 2013. A few field values can contain comments (i . in User-Agent, Server, Via fields), which can be ignored by software. Many field values may contain a quality (q) key-value pair separated by equals sign, specifying a weight to use in content negotiation. For example, a browser may indicate that it accepts information in German or English, with German as preferred by setting the q value for de higher than that of en, as follows: Accept-Language: de; q=1 , en; q=0