Trigger update of page fragment using js

What is triggering the the Ajax action? Is it controlled by a page element which is inside or outside the fragment in question? Is it controlled by some other means (e.g. a timer)?

There is no "official" support for that use case in authcache. You might be able to work around that in the following way:

1. Create a fake DOM element with the placeholder markup, e.g. something like $('<span class="authcache-ajax-frag" data-p13n-frag="block/commerce_cart-cart"></span>')
2. Insert it at the appropriate place in the DOM
3. Call Drupal.attachBehaviors() on the parent node.

Call authcache_p13n_session_invalidate() as part of your Ajax callback. This will result in the cache busting cookie (aucp13n) being set to a new random value.

Oh, wait. There is a static cache in authcache_ajax.js. So the cache busting cookie will not help.

Consider the following function (taken from authcache_ajax.js):

  function authcacheGet(url, callback, type) {
    if (cache.hasOwnProperty(url)) {
      callback(cache[url]);
    }
    else if (pending.hasOwnProperty(url)) {
      pending[url].push(callback);
    }
    else {
      pending[url] = [callback];

      $.ajax({
        url: url,
        data: {v: $.cookie('aucp13n')},
        dataType: type,
        // Custom header to help prevent cross-site forgery requests.
        beforeSend: function(xhr) {
          xhr.setRequestHeader('X-Authcache','1');
        },
        success: function(data, status, xhr) {
          cache[url] = data;
          $.each(pending[url], function() {
            this(data);
          });
          delete pending[url];
        }
      });
    }
  }

I guess it would be possible to make your use-case work if the v parameter would be added to the URL before checking the static cache.

The cache key doesn't use the v parameter.

Yes, that's what I tried to express above, and yes, patches are welcome :)

If cache-busting does not affect the static cache, then this could be considered a bug. How about just nuking the cache if the cache-busting cookie changed in the meantime?

The test fail is not related to this patch. I've seen that before in other issues. Although very strange that the branch tests is not affected.

As for the patch, I'd prefer something which does not leak internals. I'd like to avoid that future changes to the static cache will break existing sites. Can you take a look at #13 and report back whether it addresses your use-case?

Committed #13. Thank you for reporting this issue and for actively working on a solution.

Could someone point out please, what the JS would look like, to manually reload/refresh a block. As an non pro I found the authcache_ajax.js very hard to read.