Support different caching by cookie value

@theduke:

I'm trying to get your Boost patch for Context Breakpoint working.

I've successfully patched Boost (I think) and enabled it on my server and I have Context Breakpoint configured to "Save resolution in cookie"

I can see that Boost is working but I don't know what settings to modify to in Boost to preserve the Context Breakpoint cookie.

Can you point me in the right direction?

(BTW, when applying the patch file using OS X, the patcher hung unless I used the --verbose option... maybe the patch didn't actually work?)

Thanks!

@theduke:

Alternatively, could you send me the patched version of Boost that you have working?

Hey Duke,

Wanted to leave my experience related to this patch. I successfully applied the first patch you provided: "boost-cookie-inclusions.patch" to the dev version of boost. This was a life saver, as it has allowed boost to work in the majority of cases.

As expected, I am getting files created in my cache directory based on a "context_breakpoints" cookie that controls some changes on the website. This works great on all pages where only one context is triggered, and i see the following in my cache directory (starting from a clean cache):

• jobs__context_breakpoints=narrow-normal-banner.html

The above file is being served, I can tell because the comment is added to the bottom of the page source when I view it.

However, I have more than one context that is triggered on some devices (and on small browser windows), so when I visit the same jobs page in that scenario (with two contexts being triggered) I see the following file being generated:

• jobs__context_breakpoints=mobile-banner,mobile-home-layout.html

The cached file is generated without a problem, but that page is never served on subsequent page requests (no comment at the bottom of the HTML that is generated). I can visit the cached file directly in a browser without a problem.

In order to eliminate the possibility that one of those two contexts is causing the issue, I have disabled each one in turn and can confirm that the files are being created and served as expected.

However, when both are enabled, the cached file is created and not served.

The output in watchdog matches that file as well (replaced host name with abc):

Array
(
    [scheme] => http
    [host] => abc
    [path] => jobs
    [query] => 
    [full_path] => jobs
    [base_path] => /
    [query_array] => Array
        (
        )

    [url_full] => cmk.abc.com/jobs_
    [url] => http://cmk.abc.com/jobs
    [url_decoded] => /jobs_
    [base_dir] => cache/normal/cmk.abc.com/
    [filename] => cache/normal/cmk.abc.com/jobs__context_breakpoints=mobile-banner,mobile-home-layout.html
    [directory] => cache/normal/cmk.abc.com
    [normal_path] => node/7
    [path_alias] => jobs
    [args] => Array
        (
            [0] => node
            [1] => 7
            [2] => 
        )

    [menu_item] => Array
        (
            [page_type] => page
            [page_id] => 7
            [path] => node/%
            [load_functions] => Array
                (
                    [1] => node_load
                )

            [to_arg_functions] => 
            [access_callback] => node_access
            [access_arguments] => a:2:{i:0;s:4:"view";i:1;i:1;}
            [page_callback] => node
            [fit] => 2
            [number_parts] => 2
            [tab_parent] => 
            [tab_root] => node/%
            [title] => Employment
            [title_callback] => node_page_title
            [title_arguments] => a:1:{i:0;i:1;}
            [type] => 6
            [description] => 
            [position] => 
            [weight] => 0
            [include_file] => 
            [delivery_callback] => 
            [context] => 0
            [theme_callback] => 
            [theme_arguments] => Array
                (
                )

            [href] => node/7
            [tab_root_href] => node/7
            [tab_parent_href] => 
            [options] => Array
                (
                )

            [access] => 1
            [localized_options] => Array
                (
                )

            [original_map] => Array
                (
                    [0] => node
                    [1] => 7
                )

            [status] => 200
            [extra_arguments] => 
        )

    [is_cacheable] => 1
    [header_info] => Array
        (
            [status] => 200 OK
            [status-number] => 200
            [content-type] => text/html; charset=utf-8
            [content-type-basic] => text/html
            [charset] => utf-8
            [headers_sent] => 
        )

    [matched_header_info] => Array
        (
            [enabled] => 1
            [gzip] => 1
            [extension] => html
            [lifetime_max] => 1800
            [lifetime_min] => 60
            [comment_start] => <!-- 
            [comment_end] => -->
        )

)

The only difference in the file names being generated that stuck out at me is the comma that is being placed between the two context names. Could this be preventing .htaccess from matching the cached file?

Happy to provide any additional details you may need. I'm going to keep investigating, but wanted to leave this here before I forgot about.

Thanks again for your work.