HTTP headers | Origin

HTTP headers | Pragma

Last Updated : 28 Nov, 2019

The Pragma is a no-cache general-type CORS-safe listed response header field in an HTTP/1.0 header which is intended to use in the request-response chain. A pragma header meant to prevent the client from caching the response, pragma means the browsers to tell the server and any intermediate caches that it wants a fresh version of the resource and vice-versa is not true. Note: Pragma is not specified for HTTP responses that's why it is not a reliable replacement for the general HTTP/1.1 Cache-Control header. It is used only for backwards compatibility with HTTP/1.0 clients. Difference between Pragma and Cache-control headers: The Pragma is only defined as applicable to the requests by the client, and the Cache-Control may be used by both the requests of the clients and the response of the servers. Syntax

Pragma: no-cache

Directives: It is same as Cache-Control: no-cache header. It forces the caches to submit the request to the origin server for validation before releasing a cached copy. Example:

Pragma: no-cache

To check the Pragma in action go to Inspect Element -> Network check the header for Pragma like below. Pragma header is highlighted.

Browser Compatibility: The browsers compatible with Pragma header are listed below:

Google chrome 6.0 and above
Internet Explorer 9.0 and above
Firefox 4.0 and above
Opera 11.1 and above
Safari 5.0 and above
Samsung Internet

HTTP headers | Origin

M

ManishaYadav30

Improve

Article Tags :

Similar Reads

HTTP headers | Range

HTTP headers are used to pass additional information with HTTP request or response. HTTP range is an HTTP request header that is used to get part of a document from the server. If the server returns the part of the document, it uses the 206 (Partial Content) status code. If ranges are invalid status

HTTP headers | Via

The HTTP headers Via is used to inform the server of proxies through which the request was sent. The Via general is added by. It tacks the messages forwarded, request loops avoided, and identify the protocol capabilities of the sender. The header type of Via is the General type. Syntax: Via: [ <p

HTTP headers | Origin

The Origin HTTP Header is a response HTTP header that indicates the security contexts that initiates an HTTP request without indicating the path information. The Origin header is added by the browser and can not be controlled by the user. Syntax: Origin: <scheme> "://" <hostname> ":"

HTTP headers | SourceMap

The HTTP SourceMap header is a response-type header used to map original source from the transformed source. For example, the Javascript resources are transformed to some other source from its original by the browsers at the time of execution. In the process of debugging, it is too difficult to debu

HTTP headers | Vary

The HTTP Vary header is a response-type type header. It is used to indicate which headers it used when selecting a representation of a resource in a content negotiation algorithm and determines how to match future request headers to decide whether a cached response can be used rather than requesting

HTTP headers | Trailer

The HTTP Trailer header is a response header that indicates the given set of header fields is present in the trailer of a message encoded with chunked transfer-coding and allows the sender to include additional fields at the end of chunked messages in order to supply metadata. Syntax: Trailer: heade

HTTP headers | Warning

The HTTP headers allows the customer and server to pass additional information with an HTTP solicitation or response. The Warning general HTTP header entertains the information about potential problems with the status of the message which might not be reflected in the message. The field itself consi

HTTP headers are key-value pairs sent in HTTP requests and responses, providing essential information about the communication between the client and server. They include details such as content type, encoding, cache control, authentication, and more, helping manage the behavior of HTTP transactions.

HTTP Headers | TE

The HTTP TE(also known as Accept-Transfer-Encoding) is a request-type header that specifies the transfer encodings that the user is willing to accept. It is very similar to the Transfer-Encoding response header. The difference is that this header uses another directive called trailers which is very

HTTP headers | Tk

The HTTP Tk header is a response-type header it is used to indicates the tracking status that applied to the corresponding request. Syntax: Tk: ! (under construction) Tk: N (not tracking) Tk: T (tracking) Tk: C (tracking with consent) Tk: P (potential consent) Tk: D (disregarding DNT) Tk: U (updated