I've implemented varnish successfully with Turpentine and now my header and footer is replaced with the message ESI processing not enabled.
If I disable the esi blocks under cache management, the header and footer are then displayed.
I'm not sure where to begin to properly diagnose to resolve the issue. The following is part of my system.log file when I had enabled the debugging option:
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: root
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: head
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: head.calendar
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_notices
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: header
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: menu
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: notifications
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: notification_baseurl
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: cache_notifications
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: notification_survey
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: notification_security
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: notification_toolbar
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: notification_window
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: index_notifications
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: tax_notifications
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: adminhtml.system.config.switcher
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: left.child1
2014-04-07T20:19:29+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: content
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: aw_all_jsinit
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: moneybookers_jsinit
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: content.child2
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: ANONYMOUS_29.child0
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: formkey
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: ANONYMOUS_29.child1
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: ANONYMOUS_29.child1.child0
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: footer
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: js
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: js.child0
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: js.child1
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: js.child2
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: profiler
2014-04-07T20:19:30+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: before_body_end
2014-04-07T20:19:45+00:00 DEBUG (7): TURPENTINE: Cleared ESI cache for client (crawler-session) on event: catalog_controller_product_view
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: root
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: head
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: js_cookies
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: optional_zip_countries
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: addthis_smartlayers
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: after_body_start
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: google_analytics
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: turpentine_notices
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_notices
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: header
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: header
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: breadcrumbs
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: global_messages
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: global_messages
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: content
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.extrahint
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.extrahint.qtyincrements
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: ANONYMOUS_112
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: alert.urls
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: productalert.price
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: productalert.stock
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.simple
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.simple.extra
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.simple.extra.child0
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: ANONYMOUS_113
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.other
2014-04-07T20:19:45+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.media
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.additional.recurring.schedule
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.additional
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.info.tabs
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: description_tabbed
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: additional_tabbed
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: upsell_products_tabbed
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: custom
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: ANONYMOUS_114
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: custom1
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: product.tooltip
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: external.pagecache.cookie
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: footer
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Block check passed, injecting block: footer
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: before_body_end
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: piwik_analytics
2014-04-07T20:19:46+00:00 INFO (6): TURPENTINE: Checking ESI block candidate: core_profiler
2014-04-07T20:19:46+00:00 DEBUG (7): TURPENTINE: Set Varnish cache flag header to: 1
2014-04-07T20:19:46+00:00 DEBUG (7): TURPENTINE: Set ESI flag header to: 1
Other possible relevant information: Centos 6.5, Magento 1.8, Apache 2.2. Varnish 2.1.5, Redis 2.4
How can I troubleshoot the ESI processing not enabled error message that appear in the header and footer of my website?
I understand that this section does not cover third party modules, however since there have been numerous recommendations to implement this in a magento installation I hope an exception can be made.