Magento – how to set no-cache HTTP headers in controller in magento 2

full-page-cachehttp-headermagento2session

I have read in Magento 2 Dev Docs for Public content we can set no-cache HTTP headers for Controllers that don’t use layouts(last line in page).

Controllers that don’t use layouts should set no-cache HTTP headers.

I have a controller which use data from session object and when we enable FPC it doesn't work.

So I'm thinking to set no-cache HTTP headers for that controller may get data from the session object.

Let me know if I'm wrong somewhere.

Thanks

Best Answer

If you look in

vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor

Line 85 onwards:

$response = $this->_responseFactory->create();
$response->setRedirect($redirectUrl, $redirectCode);
$response->setNoCacheHeaders();
return $response;

That may help. Good luck!

Related Solutions

Magento – Controller _forward and Full Page Cache

I think it is better to do it next way:

Create observer on post dispatch

Check there if category matches the category in question - set no_cache param into the request:

    $request = $observer->getEvent()->getControllerAction()->getRequest();
    $request->setParam('no_cache', true);

(see Enterprise_PageCache_Model_Observer::checkCategoryState()). So, only categories which should be redirected won't be cached by FPC.

Magento – Magento creates two customer sessions with one browser for the same guest

If the wrong session is used, it is because the session_name is wrong. The session name is set in Mage_Core_Model_Session_Abstract_Varien::setSessionName().

But after a look on the Stacktrace, I have no idea, why overwriting _construct or even __construct should be a problem here:

Best Answer

Related Solutions

Magento – Controller _forward and Full Page Cache

Magento – Magento creates two customer sessions with one browser for the same guest

Related Topic