Example 2, prohibit the page from being cached in IE
Description: If the web pages on the server change frequently, set Expires to -1, indicating immediate expiration. If a web page is updated at 1 am every day, you can set Expires to 1 am the next day. When the HTTP1.1 server specifies CacheControl = no-cache, the browser will not cache the web page. Legacy HTTP 1.0 servers cannot use the Cache-Control header. So for backward compatibility with HTTP 1.0 servers, IE provides special support for HTTP using the Pragma:no-cache header. If the client communicates with the server over a secure connection (https://) and the server returns the Pragma:no-cache header in the response, Internet Explorer does not cache the response. Note: Pragma:no-cache prevents caching only when used in a secure connection. If used in a non-secure page, the handling is the same as Expires:-1. The page will be cached but marked as expired immediately. http-equiv meta tag: You can use http-equiv meta to mark the specified http message header in the html page. Older versions of IE may not support html meta tags, so it's best to use http message headers to disable caching. Example 3: Let the user's browser display a file not found message. Online information shows: PHP’s function header() can send the Status header to the browser. For example:
. In fact, the response returned by the browser is:
The first part is the version of the HTTP protocol (HTTP-Version); The second part is the status code (Status); The third part is Reason-Phrase. Example 4, allowing users to download files (hidden file location) The html tag can be used to download ordinary files. If you want to keep the file confidential and you cannot tell others the file link, you can use the header function to download the file.
Example 5, enter the content before the header function Generally speaking, HTML content cannot be output before the header function. Similarly, there are setcookie() and session functions. These functions need to add message header information to the output stream. If there are echo statements before header() is executed, when header() is encountered later, a “Warning: Cannot modify header information – headers already sent by….” error will be reported. There cannot be any text, blank lines, carriage returns, etc. in front of these functions, and it is best to add the exit() function after the header() function. For example, the following incorrect writing has a blank line between the two php code snippets:
Cause analysis: When a PHP script starts executing, it can send http message header (title) information and body information at the same time. The http message header (from the header() or SetCookie() function) is not sent immediately, instead, it is saved to a list. In this way, the title information can be modified, including the default title (such as the Content-Type title). However, once the script sends any non-header output (for example, using HTML or a print() call), then PHP must first send all headers and then terminate the HTTP header. Then continue to send the main data. From this point on, any attempt to add or modify Header information is not allowed, and one of the above error messages will be sent. Solution: Modify php.ini to turn on caching (output_buffering), or use the caching functions ob_start(), ob_end_flush(), etc. in the program. Principle analysis: When output_buffering is enabled, PHP does not send HTTP headers when the script sends output. Instead, it pipes this output into a dynamically growing cache (only available in PHP 4.0, which has a centralized output mechanism). You can modify/add headers, or set cookies, because headers are not actually sent. When all scripts terminate, PHP will automatically send HTTP headers to the browser, and then send the contents of the output buffer. Attached are some other examples of php header functions.
|