Windows | Mac OSX | Linux | ||
---|---|---|---|---|
Internet Explorer | 8 or greater | |||
Internet Explorer | 7 | |||
Firefox | 4 or greater | |||
Firefox | 3 | |||
Safari | 3 or greater | |||
Opera | 7 or greater | |||
Google Chrome | 5 or greater |
A "cookie" is information stored by a Web site server (e.g., PubMed) on your computer. See the NLM Privacy Policy for additional information.
In the case of PubMed, it is information about your interactions that may be needed later to perform a function. Cookies allow PubMed to provide more interactive features such as Preview/Index, Clipboard, History, My NCBI and paging through results. Cookies placed by PubMed are removed from your computer after a set time period unless you choose to use a persistent cookie with the My NCBI automatic sign in function.
To use these interactive features you need to enable cookies on your computer. Please consult your browser's Help for information on enabling cookies. If you have problems using cookie-dependent features of PubMed even after enabling cookies, possible reasons may include:
NCBI has enabled the use of accesskeys for easier keyboard navigation of common links and page elements within our pages and our site. Because browsers implement accesskeys differently, even on different operating systems, we have also provided a list of browser accesskeys and actions.
NCBI is using HTTP1.1 compression/content encoding with Entrez databases (e.g., PubMed). Data compression allows data to be sent faster - a big help for users who have slower connections.
Most recent versions of popular browsers are by default enabled to use HTTP1.1. If, however, users see the message, "Warning: Page has Expired," after using the back button in their browser, they should enable HTTP1.1 compression in their browser. The steps to enable HTTP1.1 compression in Microsoft Internet Explorer (Internet Explorer) are:
If, after enabling HTTP1.1 compression (be sure to close and re-launch the browser), users still see the "Warning: Page has Expired" message, it is possible that another application is responsible. For example, we have determined that, even with HTTP1.1 compression enabled, Symantec's firewall program, Norton Internet Security can cause the browser to display the error message if the firewall is configured to monitor HTTP connections, which is the default configuration.
If, in the case of a firewall program, users wish to disable HTTP monitoring, they should fully understand the consequences of doing so. We suggest users either consult the product documentation or contact the vendor.