# werkzeug.CommonRequestDescriptorsMixin¶

class werkzeug.CommonRequestDescriptorsMixin[source]

A mixin for BaseRequest subclasses. Request objects that mix this class in will automatically get descriptors for a couple of HTTP headers with automatic type conversion.

New in version 0.5.

## Attributes¶

 content_encoding The Content-Encoding entity-header field is used as a modifier to the media-type. content_length The Content-Length entity-header field indicates the size of the entity-body in bytes or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET. content_md5 The Content-MD5 entity-header field, as defined in RFC 1864, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body. content_type The Content-Type entity-header field indicates the media type of the entity-body sent to the recipient or, in the case of the HEAD method, the media type that would have been sent had the request been a GET. date The Date general-header field represents the date and time at which the message was originated, having the same semantics as orig-date in RFC 822. max_forwards The Max-Forwards request-header field provides a mechanism with the TRACE and OPTIONS methods to limit the number of proxies or gateways that can forward the request to the next inbound server. mimetype Like content_type, but without parameters (eg, without charset, type etc.) and always lowercase. mimetype_params The mimetype parameters as dict. pragma The Pragma general-header field is used to include implementation-specific directives that might apply to any recipient along the request/response chain. referrer The Referer[sic] request-header field allows the client to specify, for the server’s benefit, the address (URI) of the resource from which the Request-URI was obtained (the “referrer”, although the header field is misspelled).