nexcess / magento-turpentine

A Varnish extension for Magento.
GNU General Public License v2.0
519 stars 253 forks source link

404 Pages + ESI processing not enabled #292

Open gallart opened 11 years ago

gallart commented 11 years ago

Hello,

On Magento 1.7.0.2 + Turpentine + Varnish 3, I'm having this message on top of all 404 pages on my e-commerce.

ESI processing not enabled

I've tried all solutions proposed in other related issues "cache clear", etc... But no luck.

Any idea?

Thanks

aheadley commented 11 years ago

Can you see if there are any messages in your webserver/PHP/Magento logs (after flushing the cache)?

gallart commented 11 years ago

Here are the logs :

2013-08-16T21:27:56+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: root
2013-08-16T21:27:56+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: head
2013-08-16T21:27:56+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: js_cookies
2013-08-16T21:27:56+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: optional_zip_countries
2013-08-16T21:27:56+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: wordpress.blog.feed
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: before_head_end
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: google_analytics
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: after_body_start
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: turpentine_notices
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_notices
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: header
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: header
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_messages
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: global_messages
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: content
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: breadcrumbs
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: page_content_heading
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: cms.wrapper
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: cms_page
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: messages
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: messages
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: wordpress_posts_associated
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: default_no_route
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left.permanent.callout
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: catalog.leftnav
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left.newsletter
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.social
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.social-fb
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: footer
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: footer
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: before_body_end
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: belvg.facebookfree.block
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.facebook
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.google
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.pin
2013-08-16T21:27:57+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: core_profiler
2013-08-16T21:27:57+00:00 DEBUG (7): TURPENTINE: Set Varnish cache flag header to: 1
2013-08-16T21:27:57+00:00 DEBUG (7): TURPENTINE: Set ESI flag header to: 1
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Matched router: default
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_messages
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Set Varnish cache flag header to: 0
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Set ESI flag header to: 0
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Matched router: default
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: messages
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: root
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: head
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: js_cookies
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: optional_zip_countries
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: wordpress.blog.feed
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: before_head_end
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: google_analytics
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: after_body_start
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: turpentine_notices
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_notices
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: header
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: header
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_messages
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: global_messages
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: content
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: breadcrumbs
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: page_content_heading
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: cms.wrapper
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: cms_page
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: messages
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: messages
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: wordpress_posts_associated
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: cms.aide
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left.permanent.callout
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: catalog.leftnav
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left.newsletter
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.social
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.social-fb
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: footer
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: footer
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: before_body_end
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: belvg.facebookfree.block
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.facebook
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.google
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: partage.pin
2013-08-16T21:27:58+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: core_profiler
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Set Varnish cache flag header to: 1
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Set ESI flag header to: 1
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Set Varnish cache flag header to: 0
2013-08-16T21:27:58+00:00 DEBUG (7): TURPENTINE: Set ESI flag header to: 0
gallart commented 11 years ago

Up ?

henryzxj commented 10 years ago

I got the same log, and all pages doesn't have the header and the footer when the Varnish ESI Blocks is enabled.

therouv commented 10 years ago

Bump.

I have the same problem: If you have for example an old product url (http://example.org/old-product-url.html) and you try to call that url, Magento just uses that url and internally call cms_index_noroute and sets the response code 404. The site is then still cached by the Turpentine module and you get the error "ESI processing not enabled" on the page.

licarna commented 10 years ago

I'm seeing this issue as well, but for a new product. The link is correct for the product too.

I have a multi-site implementation and the funny thing is that it only happens on one site.

pepijnblom commented 9 years ago

Was this ever solved? We are seeing the same problem. I've tried excluding various no_route routes in the tuerpentine_esi.xml but to no avail.

aricwatson commented 9 years ago

@pepijnblom @therouv did either of you find a solution? Can you give us steps to replicate with the default theme?

pepijnblom commented 9 years ago

@aricwatson Unfortunately no and we have totally stopped using Varnish/Turpentine and just switched to adding block caching everywhere by hand (stored in Redis) and running hhvm.

asubit commented 7 years ago

The problem is related to an incompatibility between your Magento version and Turpentine. The latest version of Turpentine requires that the varnish configuration be modified to include the following line under DAEMON_OPTS

-p esi_syntax=0x2

Once this was applied, it was necessary to restart the varnish service, apply the Varnish Config (Under Cache Management in the Admin Panel) and flush all cache.