Closed (works as designed)
Project:
Boost
Version:
7.x-1.0-beta2
Component:
Caching logic
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Aug 2010 at 23:34 UTC
Updated:
11 Sep 2013 at 12:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
mikeytown2 commentedI set the path in boost_init()
What does $_REQUEST['q'] and $_GET['q'] output on those pages?
Comment #2
root66 commentedI do have to rewrite the URL, so drupal gets the page variable:
RewriteRule (.*)/page/([0-9]*)$ $1&page=$2 [L,QSA]
Now the cache file for each page is created, but it is not loaded. I think it's because i can't change the %{QUERY_STRING}. For www.domain.tld/someview/page/123 there's no %{QUERY_STRING}, but after my rewrite it's &page=123.
RewriteCond %{DOCUMENT_ROOT}/cache/normal/%{HTTP_HOST}%{REQUEST_URI}_%{QUERY_STRING}\.html\.gz -s
Comment #3
mikeytown2 commentedwhat gets saved in the cache folder when you hit the pager?
somenode/page/1
OR
somenode?page=1
Comment #4
root66 commentedsomenode_page=1.html
Comment #5
mikeytown2 commentedgive this a shot; be sure to enable the new setting
Comment #6
root66 commentedNow there's a new cache-subdirectory called "page" containing files like 1_.html, 2_.html, 3_.html (for each page), but the htaccess rule doesn't redirect to them.
Thanks for your help so far!
Comment #7
mikeytown2 commentedput this
below the boost rules; they where above correct?
Comment #8
root66 commentedIt's working now. The problem was the %{HTTP_HOST} in the boost rules, because my test server runs at port 8080 and there's no caching directory named host:port. It's 'host' only (without the port). Is there a mod_rewrite variable which contains the hostname only, without the port?
Comment #9
mikeytown2 commentedone way to find out; run this
Comment #10
mikeytown2 commentedComment #11
Andrew Gorokhovets commented+1
Comment #12
mikeytown2 commentedcommitted
Comment #14
Mentor.37 commentedHere same problem with drupal 7, how can i solve it?
Comment #15
Anonymous (not verified) commentedHave you been through the thread above? In particular, what if anything is being created in the cache ?
Comment #16
Mentor.37 commentedI'm on drupal 7 with and the post is for drupal 6 so the patch is not working.
With Clean Pagination I have problems with blog and taxonomy terms. The problem is the same of this.
I'm using Clean Pagination to have my pagers from www.site.com/blog/user?page=1 to www.site.com/blog/user/page/1 and Boost only caches file for www.site.com/blog, not for www.site.com/blog/user/page/1.
Same problem with taxonomy.
If I have www.site.com/taxonomy_term and www.site.com/taxonomy_term/page/1 Boost only cache taxonomy_term.
Comment #17
Anonymous (not verified) commentedWhat I meant when I wrote, have you gone through the thread, is what have you got in your cache being generated. Is the additional rewrite rule working? have you read this post on the pagination module appearing to conflict with boost and global redirect
#1285824: what would you do for the front page?
Comment #18
Mentor.37 commentedI have no problem with global redirect.
I added without success the additional rewrite rule.
The problem only exists for taxonomy and blog, for the frontpage all works without problem.
For example for frontpage i have:
www.site.com/frontpage
www.site.com/frontpage/page/1
www.site.com/frontpage/page/2
and in cache folder i have the file:
frontpage_.html
and the folder:
frontpage/page
with subfolders:
1
2
But with blog and taxonomy terms i do not have the folders in cache.
Comment #19
Anonymous (not verified) commentedIf the rewrite rule is removed then does the front page fail to cache?
Comment #20
Mentor.37 commentedWith or without rewrite rule there is no problem for the frontpage.
Comment #21
Mentor.37 commentedAny help?
Comment #22
Anonymous (not verified) commentedSo the original fix worked with a pager on the front page but not under differing pages and the rewrite rule does nothing for any situation (so can be excluded), so we go back to the time honoured boost debug, which is
Comment #23
Mentor.37 commentedThe pager on the front page works without problem without any fix.
The ohter pages do not works with and without rewrite rule.
For other questions:
1: For these pages drupal only place in the cache the first page
2: Yes in the not cached pages there is the DRUPAL_UID cookie
3: In the log there are not any error
Thank's for your help.
Comment #24
Anonymous (not verified) commentedThe DRUPAL_UID cookie is set when a drupal session is opened, it would appear from the information you provided that on the uncached pages one of you modules is starting up a drupal session for an anonymous user (possibly because they want to store the page number), this is therefore not a boost issue but one caused by the modules involved that should set their own cookie rather than initiate a drupal core function.
Effectively one of the modules involved is "fake" logging in a user so boost disables as otherwise boost could do things like display private user information like cached versions of edited pages.
Comment #25
Mentor.37 commentedSorry, my error, i was logged-in in other tab, there is not DRUPAL_UID cookie for cached and not cached pages.
Sorry.