Releases for Boost

• #1398578: Apache has problem with urlencoded query strings in cached file names by mow, DamienMcKenna, jamix, Philip_Clarke, bendev
• #1957532: Boost with Redirect Module and 301 by azinck

Fix Data leakage via the form cache

• #1181632: clearing cache shouldn't truncate boost_cache_settings table : do not truncate boost_cache_settings table on cache flush (it contains real settings that are set by the user)

This is the first release of Boost 6.x-1.x since 1.18 was released, more than two years ago. Since then, the dev version had evolved, but no formal release had been made. This version is identical to 6.x-1.19-beta1 (no issues had been reported). The 6.x-1.19 release was not good, since it was not tagged correctly.

Recent changes include:

This is the first release of Boost 6.x-1.x since 1.18 was released, more than two years ago. Since then, the dev version had evolved, but no formal release had been made.

Recent changes include:

Highly Experimental. Expect changes.
Advanced features you want will not be in here right now.
http://drupalcode.org/project/boost.git/log/refs/heads/7.x-1.x

Notes:
I've created some Lighttpd rules for boost, testing of them would be appreciated.
Exposed views filters are now properly cached.
This should be a very stable release, with no actively known bugs.

Known Issues:
#629682: Error message on new install. - Annoying bug that does not effect how boost works.
#631452: Table doesn't exist in multisite setup
#630174: warning: md5() expects parameter 1 to be string, array given in /site/sites/all/modules/boost/boost.module on line 1921

This should be an awesome release. Please report any bugs or WTF's you encounter.

Notes:
I was able to identify a bug with the FieldAPI so the beginning part of the buttons on the boost page have a number added to them as a way to get around the bug; or at least identify when Drupal is screwing up, and prevent the wrong operation from taking place.
The flush button will now say flush or expire based on your settings. If that page is already expired then it will always say flush.
You can now leave the url_alias option turned on in the crawler and it will be smart about what url's it crawls.
Multi site flushing works a lot better now.
301 redirects are now killed from the cache (404 & 403 where already taken care of).
Overwriting of the cache is no longer required for "Do not flush expired content on cron run, instead recrawl and overwrite it" to work. This BTW is a huge win for performance.

Bug Fixes:
#621668: Large Websites & boost_tree_directory() function don't play along
#621870: Set time limits when dealing with the file system
#623784: Gzip corruption when saving data-stream if using pressflow and built in cache and boost at the same time
#623578: boost_stats.php & drupal_json missing
#623516: Based on settings have flush button say flush or expire
#623536: Expiration validation (be smart in short)
#624026: Make the "Flush all sites caches in this database (singe db, multisite)" work better
#625014: boost_cache_kill() is very database intensive
#625962: _boost_index_exists should grab Column_name instead of Key_name
#626634: Call time pass by reference...

Feature Requests:
#623540: Allow setting of url import bulk size
#478644: Cache file path shouldn't be stored in the DB by default
#613926: Better url_alias behavior in crawler
#627844: Kill old paths from cache if a 301 was given
#629470: Set boost tag in header

Known Issues:
#617826: Assignment instead of comparison in boost_cache_expire_derivative() - nodeapi is not flushing the node as a result of this.

Known Issues:
#603186: Ubercart shop orders become unavailable right after Boost module installation - Workaround for a bug in Ubercart that will be fixed in their next release.

opps...

Get 1.10

Known Issues:
#591098: Multisite setup wont start - Multisite & single database.
#590704: I have no crawler action... - 6.14 is caching crawler requests if core cache enabled.

Notes:
Because of new menu changes, you need to press the Clear cached data button located on the "admin/settings/performance" page.

If your using the latest version of Authcache, there is a slight chance Boost will not work with it. To get around this issue, disable this setting in Boost:

admin/settings/performance/boost
Boost advanced settings
Asynchronous Opperation: output HTML, close connection, then store static file.
_{Run php in the background. When a cached page is generated, this will allow for faster page generation; downside is the headers are not the standard ones outputted by drupal; sends "Connection: close" instead of "Connection: Keep-Alive".}

Out fairly quickly due to several bug fixes.

Hopefully the last RC!

This release fixes a bunch of issues
#513924: Cache not expired if edit managed directly from content list
#513860: Wrong redirect after user registration.

You can grab the new rules on the performance page under Apache .htaccess settings generation. Right now it generates the rules for boosted1.txt; looking into making it do others. Detects subdir installs and generates the correct rules.

.htaccess updated

In order for the one of the bug fixes and the new features to work, you need to upgrade your old .htaccess file. The new rules can be copied from boosted1.txt or boosted2.txt depending on your setup.

The first alpha release for Drupal 6.x.

Changes since release 5.x-1.0:

• #238290: Drupal 6.x port by bhuga: Branched module for Drupal 6.x.
• #178914: Prevent the cache from getting wiped when site goes off-line: Ensure the static page cache gets wiped when the site is taken offline.
• #289674: Supporting cached pages for authenticated users: Got rid of the embedded user ID in the cache directory name. It only annoyed people, and as long as the module only supports anonymous users it is simply of no use. In the future, avoid premature feature creep.
• #289674: Supporting cached pages for authenticated users: Removed cache directory user ID material from README.txt.
• #289674: Supporting cached pages for authenticated users: Corrected a user ID-related relic in the Boost .htaccess rules.
• #311988: Prevent caching 404 Not Found responses: Prevent caching any HTTP responses other than those of type 'text/html' and status '200 OK'.
• #192596: Expire cached page when comment deleted by torres: Expire cached page when a comment is unpublished or deleted.
• #242145: Don't run boost on cron?: Implemented a new setting for configuring whether to purge expired cache files on cron runs or not.
• #325281: Add StandAgainstPoverty.org to USERS.txt by Ian Ward.
• #325309: Add EWG.org to USERS.txt by Justin Miller.
• #323395: SERVER_NAME vs HTTP_HOST in rewrite rules: Supply boosted .htaccess templates for both SERVER_NAME and HTTP_HOST configurations.

This release fixes a security vulnerability, all users of boost-5.x prior to 1.0 are urged to upgrade. For more details, see SA-2007-022.

The first more-or-less stable version for Drupal 5.x, and a highly recommended upgrade for all users of any previous development snapshots.

The very latest version for Drupal 5.x. Tends to be relatively stable, with new features only occasionally being merged or backported into CVS. Recommended for expert users who feel comfortable submitting bug reports for the occasional unexpected glitch.