Changeset 1506285
- Timestamp:
- 10/01/2016 05:37:21 AM (10 years ago)
- File:
-
- 1 edited
-
add-headers/trunk/readme.txt (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
add-headers/trunk/readme.txt
r1383725 r1506285 1 1 === Add Headers === 2 2 Contributors: gnotaras 3 Donate link: http://bit.ly/wp-add-headers 4 Tags: caching, headers, expires, cache-control, last-modified, etag, seo, if-modified-since, if-none-match, if-match, if-range, cache, http, web, server, response, optimize, bandwidth, server load, cpu load 3 Tags: 5 4 Requires at least: 3.1.0 6 5 Tested up to: 4.5 … … 16 15 Adds the *ETag*, *Last-Modified*, *Expires* and *Cache-Control* headers to HTTP responses generated by WordPress for more efficient caching. 17 16 18 = Before reading any further = 17 **NOTICE:** THIS PLUGIN HAS BEEN **DEPRECATED**. IT IS NO LONGER SUPPORTED. IT IS NO LONGER TESTED WITH NEW WORDPRESS RELEASES. USING IT IN PRODUCTION IS NOT RECOMMENDED. 19 18 20 Before reading any further or trying this plugin on your WordPress platforms and, especially before adding a rating, please **make sure** you have thoroughly studied the [FAQ](http://www.codetrax.org/projects/wp-add-headers/wiki/FAQ). This plugin might not be what you think it is. Also, this plugin might not be the right plugin for you.19 IT IS STRONGLY SUGGESTED TO MIGRATE TO OTHER MORE MODERN AND BETTER MAINTAINED PLUGINS. 21 20 22 = Notice regarding the functionality of 2.X.X releases = 21 IF YOU ARE STARTING A NEW BLOG, IT IS HIGHLY RECOMMENDED TO SEARCH FOR OTHER PLUGINS IN ORDER TO AVOID THE INEVITABLE FUTURE MIGRATION. 23 22 24 In Add-Headers releases older than 2.0.0 caching was enabled by default. This resulted in several users, who didn't have the required knowledge about HTTP caching, assuming that the plugin would somehow auto-configure itself according to their web sites' special needs. So, since 2.0.0, no page is allowed to be cached by default and the [configuration](http://www.codetrax.org/projects/wp-add-headers/wiki/Configuration) of the plugin has become mandatory in order to make the dynamic pages cacheable. 23 REGARDING EXISTING USERS, AT THE TIME OF WRITING, THERE ARE NO MAJOR BUGS. PROVIDED THAT THE WORDPRESS API DOES NOT CHANGE SOON, YOU HAVE THE TIME TO EXPERIMENT WITH OTHER PLUGINS AND PLAN YOUR MIGRATION. 24 25 <blockquote> 26 27 <strong>Important Notice</strong> 28 29 <br /><br /> 30 31 This plugin has only been used on a very few simple blogs. Therefore, it should be considered <strong>experimental</strong>. 32 33 <br /><br /> 34 35 I do not recommend running this plugin in <em>production</em>, unless you have previously thoroughly tested it with your specific configuration, especially in complex WordPress installations. In any case, by running this plugin in production, you are on your own. 36 37 <br /><br /> 38 39 Please note that I no longer provide any information about the compatibility of this plugin with recent WordPress releases. Please, test it yourself, so as to be sure it works well with your configuration. 40 41 <br /><br /> 42 43 Due to lack of free time, there are no plans to work on this plugin in the near future. If it does not work as expected for you, I strongly suggest to look for other plugins in the WordPress Plugin Repository. 44 45 <br /><br /> 46 47 </blockquote> 25 48 26 49 = Official Project Homepage = … … 32 55 *Add-Headers* is released without support of any kind. 33 56 34 However, you can still get support free of charge at the [issue tracker](https://github.com/gnotaras/wordpress-add-headers/issues) at Github. Feel free to post your questions, suggestions, bug reports, feature requests about the _Add-Headers_ project (free registration is required in order to post).35 36 The issue tracker at Github is the **recommended support channel** for faster communication.37 38 57 = Legal Notice = 39 58 40 Add-Headers is Copyright (c) 2013-201 5George Notaras. All rights reserved.59 Add-Headers is Copyright (c) 2013-2016 George Notaras. All rights reserved. 41 60 42 61 Permission is granted to use this software under the terms of the GNU General … … 54 73 == Installation == 55 74 56 Add-Headers can be easily installed through the plugin management interface from within the WordPress administration panel.75 Add-Headers can be easily installed through the plugin management interface of WordPress. 57 76 58 77 … … 74 93 == Changelog == 75 94 76 = Notice about getting support = 95 **NOTICE:** THIS PLUGIN HAS BEEN **DEPRECATED**. IT IS NO LONGER SUPPORTED. IT IS NO LONGER TESTED WITH NEW WORDPRESS RELEASES. USING IT IN PRODUCTION IS NOT RECOMMENDED. 77 96 78 For faster communication please feel free to post your questions, suggestions, bug reports, feature requests in the [issue tracker](https://github.com/gnotaras/wordpress-add-headers/issues) at Github. 97 IT IS STRONGLY SUGGESTED TO MIGRATE TO OTHER MORE MODERN AND BETTER MAINTAINED PLUGINS. 98 99 IF YOU ARE STARTING A NEW BLOG, IT IS HIGHLY RECOMMENDED TO SEARCH FOR OTHER PLUGINS IN ORDER TO AVOID THE INEVITABLE FUTURE MIGRATION. 100 101 REGARDING EXISTING USERS, AT THE TIME OF WRITING, THERE ARE NO MAJOR BUGS. PROVIDED THAT THE WORDPRESS API DOES NOT CHANGE SOON, YOU HAVE THE TIME TO EXPERIMENT WITH OTHER PLUGINS AND PLAN YOUR MIGRATION. 79 102 80 103 = Changelog Entries = … … 83 106 84 107 - [2.0.1](http://www.codetrax.org/versions/314) 85 - This release introduces the concept of setting a different caching timeout on _old _content_. For this reason two new options have been added: [cache_old_content_threshold_seconds](http://www.codetrax.org/projects/wp-add-headers/wiki/Configuration#cache_old_content_threshold_seconds) and [cache_old_content_max_age_seconds](http://www.codetrax.org/projects/wp-add-headers/wiki/Configuration#cache_old_content_max_age_seconds). Please see this [configuration example](http://www.codetrax.org/projects/wp-add-headers/wiki/Configuration#Different-caching-timeout-for-old-content) that demonstrates this functionality.108 - This release introduces the concept of setting a different caching timeout on _old content_. For this reason two new options have been added: [cache_old_content_threshold_seconds](http://www.codetrax.org/projects/wp-add-headers/wiki/Configuration#cache_old_content_threshold_seconds) and [cache_old_content_max_age_seconds](http://www.codetrax.org/projects/wp-add-headers/wiki/Configuration#cache_old_content_max_age_seconds). Please see this [configuration example](http://www.codetrax.org/projects/wp-add-headers/wiki/Configuration#Different-caching-timeout-for-old-content) that demonstrates this functionality. 86 109 - Minor improvements and fixes. 87 110 - [2.0.0](http://www.codetrax.org/versions/313)
Note: See TracChangeset
for help on using the changeset viewer.