You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
our environment to test is Magento 1.3.2.4.
Varnish 2.1.5 and runs in same host with apache backend
VLC is VLC provided by Magneto-Varnish
Magento has caché items in APC opt code and sessions handled by Memcached in another Host.
I don't know if this version is compatible with your extension. The problem is when a item is selected, dropped, added, etc, a lot of times a CTRL+F5 is required to show correct page. It is as if cache does not refresh. I have tested some other pages with a custom rules like admin page and works good.
Maybe is an issue with my current scenario?
Thanks
The text was updated successfully, but these errors were encountered:
I just modify our test scenario, I have removed code in app/etc/local.xml about handling sessions in memcache instance and now shop is working good. We can add,remove, etc, and everything is ok, without manual refresh of customer (CTRL+F5).
So I think is very clear that there is a problem in our side, with the way to handle sessions. At least, with this setup does not work. However, I will maintain Magneto-Varnish code because the improvement is freaking crazy :) But will be fantastic if you as developer of Magneto can give us some ideas or comment something about handle sessions in Magento to avoid use filesystem.
Hi
our environment to test is Magento 1.3.2.4.
Varnish 2.1.5 and runs in same host with apache backend
VLC is VLC provided by Magneto-Varnish
Magento has caché items in APC opt code and sessions handled by Memcached in another Host.
I don't know if this version is compatible with your extension. The problem is when a item is selected, dropped, added, etc, a lot of times a CTRL+F5 is required to show correct page. It is as if cache does not refresh. I have tested some other pages with a custom rules like admin page and works good.
Maybe is an issue with my current scenario?
Thanks
The text was updated successfully, but these errors were encountered: