Drupal module Boost with https, pulling the wrong cache pages - caching

I am implementing the boost module for Drupal on my site and have run into this caching problem. The site caches pages but when visiting as an anonymous user it gives me the wrong cached pages. I am based in Ireland and expect to see the Irish version of the site but once the home page is cached it gives me the american version of the site.
Here is a list of steps I took to implement Boost
First I go to /admin/config/development/performance and disable "Cache pages for anonymous users"
Then I enabled "Boost" and "Boost Crawler" on the modules page
I go to .HTACCESS and disable "Bypass the boost cache for ssl requests" because the live site has https.
I generate the .HTACCESS and insert it into the correct place in my own .HTACCESS file
I have a feeling that I may have to write some custom code in the .HTACCESS file to get it to work but would really like some more incite before I go ahead and to that.
Currently the uncached version of the site is served up correctly in each country but is very slow.
So to summarise really what I need Boost to do for me is cache something like 200 versions of the site (thats how many countries we are serving the site to) and to serve the correct versions of the site to those countries. Is this possible and how can I implement it?
Any help is very much appreciated, Thanks.
Update 1
after adding the code here to .HTACCESS
RewriteCond %{HTTP:Accept-Language} ^et.*$ [NC]
RewriteCond %{REQUEST_URI} ^/$ [NC]
RewriteCond %{QUERY_STRING} !(^q\=) [NC]
RewriteRule ^(.*)$ /et [L,R=302]
RewriteCond %{HTTP:Accept-Language} ^fi.*$ [NC]
RewriteCond %{REQUEST_URI} ^/$ [NC]
RewriteCond %{QUERY_STRING} !(^q\=) [NC]
RewriteRule ^(.*)$ /fi [L,R=302]
and visiting the site form several different proxies I get it to cache in its country but the problem now is that it just caches the 1st country an anonymous visitor comes form.
My home page is in cache/normal/SITES_NAME/en_.html it doesn't seem to matter what site I come from Brazil, Germany, America, South Africa or Ireland it just caches the first one in en_.html and serves that to everywhere when really it needs to create a new set of cache files for each of these countries.
I've been using geopeeker.com and different proxies to view the pages from different parts of the world.

If you are using path prefix to detect language, Boost will not work.
You have to add this in your .htaccess to fix the problem.
RewriteCond %{HTTP:Accept-Language} ^et.*$ [NC]
RewriteCond %{REQUEST_URI} ^/$ [NC]
RewriteCond %{QUERY_STRING} !(^q\=) [NC]
RewriteRule ^(.*)$ /et [L,R=302]
RewriteCond %{HTTP:Accept-Language} ^fi.*$ [NC]
RewriteCond %{REQUEST_URI} ^/$ [NC]
RewriteCond %{QUERY_STRING} !(^q\=) [NC]
RewriteRule ^(.*)$ /fi [L,R=302]
This link provides further information.

Related

Htacces rewrite for magento http to https for one domain of multishop

We are looking for a solution for our htacces rewrite and have been looking all over the internet and could not find the solution. We have a multishop with 10 shops and are now going over at https and first want to test one shop and then do the others. We have set everything up correctly, but do not get the 301 redirect to work.
We have tried the following code:
RewriteCond %{HTTP_HOST} ^domain\.be$ [OR]
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://www.domain.be/$1 [R=301,L]
But with this code all pages of the other webshops will also be redirected to this domain. Can someone help us setting it up so we can start transfer to https?
You need to remove the OR.
RewriteCond %{HTTP_HOST} ^domain\.be$
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://www.domain.be/$1 [R=301,L]
If you have split each of your domains to have independent vhosts (likely) and therefore utilize a separate block for SSL and HTTP, you should think about using a Redirect 301 in the HTTP section of the vhost to reduce complexity.

Ajax generated content and Facebook scraping

I've built an AngularJS app and it contains views that could be considered different pages but the app is a single page app as in the page doesn't reload.
I've read up on using escaped fragment URLs to redirect search engines to snapshots of pages. My issue is when I try to share a page from my app on Facebook that it returns a 404, as can be seen using Facebook's open graph debug tool.
My app has a Larvel back-end feeding to an AngularJS front-end and my htaccess looks like this to redirect spiders and Facebook to the snapshots. As far as I knew this was working but I guess it's not.
<IfModule mod_rewrite.c>
<IfModule mod_negotiation.c>
Options -MultiViews
</IfModule>
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^(.*)$ http://%1/$1 [R=301,L]
RewriteCond %{QUERY_STRING} ^_escaped_fragment_=/?(.*)$
RewriteRule ^(.*)$ /%1? [NC,PT]
# Redirect Trailing Slashes...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)/$ /$1 [L,R=301]
# Handle Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]
</IfModule>
My URLS are formatted to the user like: domain.com/#!/bike/id/bike+name
and the snapshot URLs are the same just without the hash bang i.e domain.com/bike/id/bike+name
I'm really stunmped on this one. Any suggestions or pointers would be greatly appreciated.
Facebook crawlers don't execute any Javascript so they won't see/have no idea about your Angular routes. What I've done in my project is I've mirrored the routes that need the open-graph tags in the back-end.
If my server gets a request for a page with og-tags it will make the necessary API calls to get the data, and attach them to the index template. If my initial request is the a page with no og-tags, I just render the regular SPA index. (I'm using HTML5 mode for urls so could be a bit different for you)
Also note that I said initial request to the server. This means that your og-tags won't change as you navigate within your SPA, they'll just be the tags of the first page you requested. This is actually a non-issue because Facebook makes individuals request to your server.
Let me know if this is unclear, I'll try to explain better.

code igniter & mod_rewrite - one rewrite rule breaking another

I have a site built in codeigniter. We use short urls from our database & rewrite rules to redirect them to their full path.
For example,
RewriteRule ^secure-form$ form/contract/secure-form [L]
This works fine by itself. But I would like to use SSL on certain pages. I have edited the code so that if you go to one of these pages, all instances of http:// within the page are replaced with https:// but I need to rewrite the url to use it as well.
The pages all use the same template and all the content comes from the database so I can't just specify ssl on a particular directory.
The url's for the secure pages all start with 'secure' so I wrote the following rules and placed them above the other rewrites.
RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} ^/secure/?.*$
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} !^/secure/?.*$
RewriteRule ^(.*)$ http://%{HTTP_HOST}/$1 [R=301,L]
RewriteRule ^secure-form$ form/contract/secure-form [L]
RewriteRule ^secure-different-form$ form/contract/secure-different-form [L]
all other rewrite rules for specific pages follow
then the default rewrite further down...
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [L]
The problem is that when I add the rules to change the protocol, it ends up displaying 'form/contract/secure-form' in the url instead of 'secure-form'.
This renders the actual form on the page broken since it uses that url to build itself.
If I take out the rules that change the protocol, it displays secure-form in the url as it should, but the page is not secure.
What am I doing wrong?
----UPDATE----
Ooh, after over 20 hrs of searching, I think I finally have an answer. So, first time through, https is off & gets turned on. Then, because of the 301, it's run again & the page gets sent to form/contract/secure... But this time, https is on. Since the uri no longer STARTS with secure, it turns https off.
Hopefully, this will help someone else.

force https to a certain url

I know this issue has been addressed in many ways, but couldn't find any similar to this one I have now. The thing is that I have a code to force https to a certain or a particular url, but it seems that the (s) letter can be removed by hand so the url goes with http instead!! I mean I want the https to be force again in case the url is changed from https to http.
I hope it is a clear explanation.
RewriteCond %{SERVER_PORT} 443
RewriteCond %{REQUEST_URI} main
RewriteRule ^(.*)$ https://www.domain.com/folder1/folder2/login$1 [R,L]
does this code redirect again in case https is changed??
Thanks
Update #1
I got the meaning of what I want to point out to. It is called "blocked crawling of https"
Do this:
RewriteCond %{REQUEST_URI} main
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://www.domain.com/folder1/folder2/login$1 [R,L]

How do I redirect to a page after a file download has been initiated with mod_rewrite?

Just as the title states. Say an individual accesses a file from my database, http://domain.com/database/file.zip. Once that file download has been initiated, I wish the browser to be redirected to the database directory again. Here's what I have so far:
RewriteEngine On
Options +FollowSymLinks
RewriteRule ^Database(.zip)$ http://domain.com/db/index.html [R=301,L]
But, I get a 500 error.
And if I am being too picky, it would be nice to ignore this function on links such as: &file=something.zip.
Either way, getting the first portion to work would be fantastic.
Edit!
Here is what worked for me in the end. Cheers!
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} .*zip$|.*rar$|.*tar$|.*txt$ [NC]
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !domain\.com [NC]
RewriteRule ^(.*)$ /dl.php?url=%{REQUEST_FILENAME} [L]
Not really possible with mod_rewrite the way you have described: once the server has started delivering content (sent a 200 status code) there is no way to initiate a second response without a corresponding second request.
If you want to do this you'll have to do it on the client side: for example launch the download targetting a separate, hidden iframe and if the download starts then you can change the page location using window.location.

Resources