Hi, 
I found caching issue in K2 item view (K2 2.10.3, Joomla 3.9.28).
In com_k2/views/item/view.html.php is called function 

JResponse::allowCache(true);

This causes that Expires header is set to response by Joomla 15 minutes in future, regardless caching is enabled or not. What it cause is if user is logged in, opens some K2 article, then log out, and display the article again, the whole page is still displayed as he is logged in (browser takes it from disk cache, not from server). An opposite, user is not loggedn in, displays an article (which is for example just for logged in users), login then, go back to article, and page is still disaplyed as he is not logged in.

Moreover, when cache is enabled in Joomla global configuration System K2 plugin adds expiration header just for guests. This solves issue Logged in -> logout, but opposite still remains. So when user is not loggedn in, then login, he still sees wrong page, as he is not logged in. 

There is 'x-logged-in' header, however this seems to work only when Varnish cache is installed on server.

I didn't find way, how to disable this behavior, without hacking K2. Is this known issue, or am I doing something wrong?

thanks

Pavel

Hi,

Same issue here.

K2 v2.10.3  is overriding the default Joomla headers with its Custom HTTP headers and there is no way to disable them.

JResponse::setHeader('Cache-Control', 'public, max-age='.$cacheTTL.', stale-while-revalidate='.($cacheTTL*2).', stale-if-error='.($cacheTTL*5), true);
JResponse::setHeader('Expires', gmdate('D, d M Y H:i:s', time()+$cacheTTL).' GMT', true);

We have articles that show a summary for guests or the full content for members. It doesn't work anymore with these headers. Once the article is cached with a long expiration, it is not requested again by the browser when the user logs in.

Best Regards




 

Going back to K2 v2.9, these were the only custom headers:

        // Custom HTTP headers
        $user = JFactory::getUser();
        if (!$user->guest) {
            JResponse::setHeader('X-Logged-In', 'True', true);
        } else {
            JResponse::setHeader('X-Logged-In', 'False', true);
        }
        JResponse::setHeader('X-Content-Powered-By', 'K2 v'.K2_CURRENT_VERSION.' (by JoomlaWorks)', true);

 

The new headers were introduced between K2_v2.10.2 and K2_v2.10.3.

Best Regards

Two more places where K 2.10.3 forces the expiration header:

plugins/system/k2/k2.php, line 717
JResponse::allowCache(true);

components/com_k2/views/item/view.html.php
JResponse::allowCache(true);

If these lines are enabled, Joomla sends a header with expiration +15'

// Expires.
$this->setHeader('Expires', gmdate('D, d M Y H:i:s', time() + 900) . ' GMT');

 

Hi, great news!

It would be great if we could have the same headers as before.

It is not clear to me the benefits of emitting custom headers (Cache-Control, Expires, and Pragma) in the K2 System Plugin (onAfterInitialise).

BTW: Thank you for your recipe for Varnish ! It helped a lot to handle traffic on a massive site.

Best Regards,
Anibal Sanchez - Extly.com

 

I've updated to the latest version 2.11, and the issue is still active.

I've opened the issue on GH to follow the case there: github.com/getk2/k2/issues/556

Best Regards