nexcess_net

Turpentine - Varnish Cache

  • Popularity Score 7548 Popularity Score

    Popularity ScoreReferrals to Site/Downloads

    0 0 1+ 1+ 250+ 250+ 1000+ 1000+ 10000+ 10000+

Simplify Varnish management and deployment with Magento.
Compatible with:
This extension is currently unavailable on Magento Connect. Please contact the developer.

You will be re-directed to the developer's website to complete your purchase.

You must be registered and logged in to get extension key.
In order to get this extension, you must be logged in to the Magento Community. Click here to login or register.

Magento Connect 2.0

Magento Connect 2.0

FREE
Previous Next
Overview

Turpentine - Varnish Cache

Nexcess.net Turpentine Extension for Magento

Turpentine is a full page cache extension for Magento that works with Varnish, a very fast caching reverse-proxy. By default, Varnish doesn't cache requests with cookies and Magento sends the frontend cookie with every request causing a (near) zero hit-rate for Varnish's cache. Turpentine configures Varnish to work with Magento and modifies Magento's behaviour to significantly improve the cache hit rate.

Note that while this extension is now considered stable, it is strongly recommended that it be tested on a development/staging site before deploying on a production site due to the potential need to add custom ESI policies for blocks added by other extensions.

Features

  • Full Page Caching, with hole-punching via Varnish ESI and/or AJAX, even for logged in visitors
  • Configurable via standard Magento methods (Admin system configuration and layout XML), no manual editing of Varnish config required for most cases
  • Able to generate and apply new Varnish VCLs (configurations) on the fly, without restarting/changing Varnish's config files or flushing the cache
  • Blacklist requests from caching by URL or parameters (SID, store, etc)
  • Configure cache TTL by URL and individual block's TTL
  • Supports multiple Varnish instances for clustered usage
  • Automatic cache clearing on actions (clearing product/catalog/cms page after saving)
  • Supports non-root Magento installs (i.e. putting Magento in /store/ instead of /) and multi-store/multi-site setups
  • Support for site-crawlers for cache warming, and includes a (basic) built-in site-crawler
  • SSL support through Pound or Nginx

Requirements

  • Magento Community Edition 1.6+ or Magento Enterprise Edition 1.11+
  • Varnish 2.1+ (including 4.0)

Installation & Usage

See the Installation and Usage pages.

Support

If you have an issue, please read the FAQ then if you still need help, open a bug report in GitHub's issue tracker.

Please do not use Magento Connect's Reviews or (especially) the Q&A for support, as it is not monitored as closely as github.

Contributing

If you have a fix or feature for Turpentine, submit a pull request through GitHub to the devel branch. The master branch is only for stable releases. Please make sure the new code follows the same style and conventions as already written code.

How it works

The extension works in two parts, page caching and block (ESI/AJAX) caching. A simplified look at how they work:

For pages, Varnish first checks whether the visitor sent a frontend cookie. If they didn't, then the request will be passed through to Magento in order generate a valid session. Note that the cookie checking is bypassed for clients identified as crawlers (see the Crawler IP Addresses and Crawler User Agents settings).

For blocks, the extension listens for the core_block_abstract_to_html_before event in Magento. When this event is triggered, the extension looks at the block attached to it and if an ESI policy has been defined for the block then the block's template is replaced with a simple ESI (or AJAX) template that tells Varnish to pull the block content from a separate URL. Varnish then does another request to that URL to get the content for that block, which can be cached separately from the page and may differ between different visitors/clients.

Notes and Caveats

  • Turpentine will not help (directly) with the speed of "actions" like adding things to the cart or checking out. It only caches, so it can only speed up page load speed for site browsing. It will remove a lot of load on the backend though so for heavily loaded sites it can free up enough backend resources to have a noticeable effect on "actions".
  • There are some technical limitations when using Varnish 2.1.x: External ESI requests are not blocked, and per-block TTLs in ESI policies are not honored (all blocks use the default TTL)
  • The core parts of Turpentine (caching and ESI/AJAX injection) work under Magento CE 1.5, but a significant portion of the auxillary functionality doesn't work due to changes to event names. That said, it would be possible to use Turpentine with Magento CE 1.5 with an understanding that it is not supported and what actions need to be taken manually. Both cache flushing (both automatic an manual) and cache warming (due to missing events that trigger the cache flushing) do not work.
  • Anonymous blocks are not able to be hole-punched. For CMS pages, it is recommended that you include the block in the page's layout updates XML and give it a name, then it can have an ESI policy like normal

Known Issues

  • Logging and statistics will show all requests as coming from the same IP address (usually localhost/127.0.0.1). It should be possible to work around this using Apache's mod_remoteip or mod_rpaf.

Demo

See the Demo Sites wiki page.

If you use Turpentine (on a production site), feel free to add your site to the list!

License

The code is licensed under GPLv2+, much of the ESI-specific code is taken from Hugues Alary's Magento-Varnish extension, which is licensed as GPLv3.

Release Notes

RELEASE-0.6.5

2015-08-27 14:02:26
  • Version number: 0.6.5
  • Stability: Stable
  • Compatibility: 1.8, 1.8.1, 1.9, 1.9.1, 1.9.2
You must be registered and logged in to get extension key.

Magento Connect 2.0

Magento Connect 2.0

Nexcess.net Turpentine Extension for Magento

Turpentine is a full page cache extension for Magento
that works with Varnish, a very fast caching reverse-proxy. By
default, Varnish doesn't cache requests with cookies and Magento sends the
frontend cookie with every request causing a (near) zero hit-rate for Varnish's cache.
Turpentine configures Varnish to work with Magento and modifies Magento's
behaviour to significantly improve the cache hit rate.

Note that while this extension is now considered stable, it is strongly
recommended that it be tested on a development/staging site before deploying
on a production site due to the potential need to add custom ESI policies
for blocks added by other extensions.

Features

  • Full Page Caching, with hole-punching via Varnish ESI and/or AJAX, even for
    logged in visitors
  • Configurable via standard Magento methods (Admin system configuration and
    layout XML), no manual editing of Varnish config required for most cases
  • Able to generate and apply new Varnish VCLs (configurations) on the fly,
    without restarting/changing Varnish's config files or flushing the cache
  • Blacklist requests from caching by URL or parameters (SID, store, etc)
  • Configure cache TTL by URL and individual block's TTL
  • Supports multiple Varnish instances for clustered usage
  • Automatic cache clearing on actions (clearing product/catalog/cms page after saving)
  • Supports non-root Magento installs (i.e. putting Magento in /store/ instead
    of /) and multi-store/multi-site setups
  • Support for site-crawlers for cache warming, and includes a (basic)
    built-in site-crawler
  • SSL support
    through Pound or Nginx

Requirements

  • Magento Community Edition 1.6+ or Magento Enterprise Edition 1.11+
  • Varnish 2.1+ (including 3.0+)

Installation & Usage

See the Installation
and Usage pages.

Support

If you have an issue, please read the FAQ
then if you still need help, open a bug report in GitHub's
issue tracker.

Please do not use Magento Connect's Reviews or (especially) the Q&A for support.
There isn't a way for me to reply to reviews and the Q&A moderation is very slow.

Contributing

If you have a fix or feature for Turpentine, submit a pull request through GitHub
to the devel branch. The master branch is only for stable releases. Please
make sure the new code follows the same style and conventions as already written
code.

How it works

The extension works in two parts, page caching and block (ESI/AJAX) caching. A
simplified look at how they work:

For pages, Varnish first checks whether the visitor sent a frontend cookie.
If they didn't, then Varnish will generate a new session token for them. The page
is then served from cache (or fetched from the backend if it's not already in
the cache), with any blocks with ESI polices filled in via ESI. Note that the
cookie checking is bypassed for clients identified as crawlers (see the
Crawler IP Addresses and Crawler User Agents settings).

For blocks, the extension listens for the core_block_abstract_to_html_before
event in Magento. When this event is triggered, the extension looks at the block
attached to it and if an ESI policy
has been defined for the block then the
block's template is replaced with a simple ESI (or AJAX) template that tells Varnish to
pull the block content from a separate URL. Varnish then does another request to
that URL to get the content for that block, which can be cached separately from
the page and may differ between different visitors/clients.

Notes and Caveats

  • Turpentine will not help (directly) with the speed of "actions" like adding things
    to the cart or checking out. It only caches, so it can only speed up page load
    speed for site browsing. It will remove a lot of load on the backend though so
    for heavily loaded sites it can free up enough backend resources to have a
    noticeable effect on "actions".
  • There are some technical limitations when using Varnish 2.1.x: External ESI
    requests are not blocked, and per-block TTLs in ESI policies are not honored
    (all blocks use the default TTL)
  • The core parts of Turpentine (caching and ESI/AJAX injection) work under Magento CE 1.5, but a significant
    portion of the auxiliary functionality doesn't work due to changes to event names. That
    said, it would be possible to use Turpentine with Magento CE 1.5 with an understanding
    that it is not supported and what actions need to be taken manually. Both
    cache flushing (both automatic an manual) and cache warming (due to
    missing events that trigger the cache flushing) do not work.
  • Anonymous blocks are not able to be hole-punched. For CMS pages, it is
    recommended that you include the block in the page's layout updates XML and
    give it a name, then it can have an ESI policy like normal

Known Issues

  • Logging and statistics will show all requests as coming from the same IP address
    (usually localhost/127.0.0.1). It should be possible to work around this using
    Apache's mod_remoteip
    or mod_rpaf.

Demo

See the Demo Sites
wiki page.

If you use Turpentine (on a production site), feel free to add your site to the
list!

License

The code is licensed under GPLv2+, much of the ESI-specific code is taken from
Hugues Alary's Magento-Varnish
extension, which is licensed as GPLv3.

RELEASE-0.6.4

2015-08-04 15:46:12
  • Version number: 0.6.4
  • Stability: Stable
  • Compatibility: 1.7, 1.8, 1.8.1, 1.9
You must be registered and logged in to get extension key.

Magento Connect 2.0

Magento Connect 2.0

Nexcess.net Turpentine Extension for Magento

Turpentine is a full page cache extension for Magento
that works with Varnish, a very fast caching reverse-proxy. By
default, Varnish doesn't cache requests with cookies and Magento sends the
frontend cookie with every request causing a (near) zero hit-rate for Varnish's cache.
Turpentine configures Varnish to work with Magento and modifies Magento's
behaviour to significantly improve the cache hit rate.

Note that while this extension is now considered stable, it is strongly
recommended that it be tested on a development/staging site before deploying
on a production site due to the potential need to add custom ESI policies
for blocks added by other extensions.

Features

  • Full Page Caching, with hole-punching via Varnish ESI and/or AJAX, even for
    logged in visitors
  • Configurable via standard Magento methods (Admin system configuration and
    layout XML), no manual editing of Varnish config required for most cases
  • Able to generate and apply new Varnish VCLs (configurations) on the fly,
    without restarting/changing Varnish's config files or flushing the cache
  • Blacklist requests from caching by URL or parameters (SID, store, etc)
  • Configure cache TTL by URL and individual block's TTL
  • Supports multiple Varnish instances for clustered usage
  • Automatic cache clearing on actions (clearing product/catalog/cms page after saving)
  • Supports non-root Magento installs (i.e. putting Magento in /store/ instead
    of /) and multi-store/multi-site setups
  • Support for site-crawlers for cache warming, and includes a (basic)
    built-in site-crawler
  • SSL support
    through Pound or Nginx

Requirements

  • Magento Community Edition 1.6+ or Magento Enterprise Edition 1.11+
  • Varnish 2.1+ (including 3.0+)

Installation & Usage

See the Installation
and Usage pages.

Support

If you have an issue, please read the FAQ
then if you still need help, open a bug report in GitHub's
issue tracker.

Please do not use Magento Connect's Reviews or (especially) the Q&A for support.
There isn't a way for me to reply to reviews and the Q&A moderation is very slow.

Contributing

If you have a fix or feature for Turpentine, submit a pull request through GitHub
to the devel branch. The master branch is only for stable releases. Please
make sure the new code follows the same style and conventions as already written
code.

How it works

The extension works in two parts, page caching and block (ESI/AJAX) caching. A
simplified look at how they work:

For pages, Varnish first checks whether the visitor sent a frontend cookie.
If they didn't, then Varnish will generate a new session token for them. The page
is then served from cache (or fetched from the backend if it's not already in
the cache), with any blocks with ESI polices filled in via ESI. Note that the
cookie checking is bypassed for clients identified as crawlers (see the
Crawler IP Addresses and Crawler User Agents settings).

For blocks, the extension listens for the core_block_abstract_to_html_before
event in Magento. When this event is triggered, the extension looks at the block
attached to it and if an ESI policy
has been defined for the block then the
block's template is replaced with a simple ESI (or AJAX) template that tells Varnish to
pull the block content from a separate URL. Varnish then does another request to
that URL to get the content for that block, which can be cached separately from
the page and may differ between different visitors/clients.

Notes and Caveats

  • Turpentine will not help (directly) with the speed of "actions" like adding things
    to the cart or checking out. It only caches, so it can only speed up page load
    speed for site browsing. It will remove a lot of load on the backend though so
    for heavily loaded sites it can free up enough backend resources to have a
    noticeable effect on "actions".
  • There are some technical limitations when using Varnish 2.1.x: External ESI
    requests are not blocked, and per-block TTLs in ESI policies are not honored
    (all blocks use the default TTL)
  • The core parts of Turpentine (caching and ESI/AJAX injection) work under Magento CE 1.5, but a significant
    portion of the auxiliary functionality doesn't work due to changes to event names. That
    said, it would be possible to use Turpentine with Magento CE 1.5 with an understanding
    that it is not supported and what actions need to be taken manually. Both
    cache flushing (both automatic an manual) and cache warming (due to
    missing events that trigger the cache flushing) do not work.
  • Anonymous blocks are not able to be hole-punched. For CMS pages, it is
    recommended that you include the block in the page's layout updates XML and
    give it a name, then it can have an ESI policy like normal

Known Issues

  • Logging and statistics will show all requests as coming from the same IP address
    (usually localhost/127.0.0.1). It should be possible to work around this using
    Apache's mod_remoteip
    or mod_rpaf.

Demo

See the Demo Sites
wiki page.

If you use Turpentine (on a production site), feel free to add your site to the
list!

License

The code is licensed under GPLv2+, much of the ESI-specific code is taken from
Hugues Alary's Magento-Varnish
extension, which is licensed as GPLv3.

RELEASE-0.6.3

2015-07-28 15:03:28
  • Version number: 0.6.3
  • Stability: Stable
  • Compatibility: 1.7, 1.8, 1.8.1, 1.9
You must be registered and logged in to get extension key.

Magento Connect 2.0

Magento Connect 2.0

Nexcess.net Turpentine Extension for Magento

Turpentine is a full page cache extension for Magento
that works with Varnish, a very fast caching reverse-proxy. By
default, Varnish doesn't cache requests with cookies and Magento sends the
frontend cookie with every request causing a (near) zero hit-rate for Varnish's cache.
Turpentine configures Varnish to work with Magento and modifies Magento's
behaviour to significantly improve the cache hit rate.

Note that while this extension is now considered stable, it is strongly
recommended that it be tested on a development/staging site before deploying
on a production site due to the potential need to add custom ESI policies
for blocks added by other extensions.

Features

  • Full Page Caching, with hole-punching via Varnish ESI and/or AJAX, even for
    logged in visitors
  • Configurable via standard Magento methods (Admin system configuration and
    layout XML), no manual editing of Varnish config required for most cases
  • Able to generate and apply new Varnish VCLs (configurations) on the fly,
    without restarting/changing Varnish's config files or flushing the cache
  • Blacklist requests from caching by URL or parameters (SID, store, etc)
  • Configure cache TTL by URL and individual block's TTL
  • Supports multiple Varnish instances for clustered usage
  • Automatic cache clearing on actions (clearing product/catalog/cms page after saving)
  • Supports non-root Magento installs (i.e. putting Magento in /store/ instead
    of /) and multi-store/multi-site setups
  • Support for site-crawlers for cache warming, and includes a (basic)
    built-in site-crawler
  • SSL support
    through Pound or Nginx

Requirements

  • Magento Community Edition 1.6+ or Magento Enterprise Edition 1.11+
  • Varnish 2.1+ (including 3.0+)

Installation & Usage

See the Installation
and Usage pages.

Support

If you have an issue, please read the FAQ
then if you still need help, open a bug report in GitHub's
issue tracker.

Please do not use Magento Connect's Reviews or (especially) the Q&A for support.
There isn't a way for me to reply to reviews and the Q&A moderation is very slow.

Contributing

If you have a fix or feature for Turpentine, submit a pull request through GitHub
to the devel branch. The master branch is only for stable releases. Please
make sure the new code follows the same style and conventions as already written
code.

How it works

The extension works in two parts, page caching and block (ESI/AJAX) caching. A
simplified look at how they work:

For pages, Varnish first checks whether the visitor sent a frontend cookie.
If they didn't, then Varnish will generate a new session token for them. The page
is then served from cache (or fetched from the backend if it's not already in
the cache), with any blocks with ESI polices filled in via ESI. Note that the
cookie checking is bypassed for clients identified as crawlers (see the
Crawler IP Addresses and Crawler User Agents settings).

For blocks, the extension listens for the core_block_abstract_to_html_before
event in Magento. When this event is triggered, the extension looks at the block
attached to it and if an ESI policy
has been defined for the block then the
block's template is replaced with a simple ESI (or AJAX) template that tells Varnish to
pull the block content from a separate URL. Varnish then does another request to
that URL to get the content for that block, which can be cached separately from
the page and may differ between different visitors/clients.

Notes and Caveats

  • Turpentine will not help (directly) with the speed of "actions" like adding things
    to the cart or checking out. It only caches, so it can only speed up page load
    speed for site browsing. It will remove a lot of load on the backend though so
    for heavily loaded sites it can free up enough backend resources to have a
    noticeable effect on "actions".
  • There are some technical limitations when using Varnish 2.1.x: External ESI
    requests are not blocked, and per-block TTLs in ESI policies are not honored
    (all blocks use the default TTL)
  • The core parts of Turpentine (caching and ESI/AJAX injection) work under Magento CE 1.5, but a significant
    portion of the auxiliary functionality doesn't work due to changes to event names. That
    said, it would be possible to use Turpentine with Magento CE 1.5 with an understanding
    that it is not supported and what actions need to be taken manually. Both
    cache flushing (both automatic an manual) and cache warming (due to
    missing events that trigger the cache flushing) do not work.
  • Anonymous blocks are not able to be hole-punched. For CMS pages, it is
    recommended that you include the block in the page's layout updates XML and
    give it a name, then it can have an ESI policy like normal

Known Issues

  • Logging and statistics will show all requests as coming from the same IP address
    (usually localhost/127.0.0.1). It should be possible to work around this using
    Apache's mod_remoteip
    or mod_rpaf.

Demo

See the Demo Sites
wiki page.

If you use Turpentine (on a production site), feel free to add your site to the
list!

License

The code is licensed under GPLv2+, much of the ESI-specific code is taken from
Hugues Alary's Magento-Varnish
extension, which is licensed as GPLv3.

RELEASE-0.6.1

2014-10-01 17:36:40
  • Version number: 0.6.1
  • Stability: Stable
  • Compatibility: 1.6, 1.6.1, 1.6.2.0, 1.7, 1.8, 1.8.1, 1.9, 1.11, 1.11.1, 1.12, 1.13, 1.13.1, 1.14
You must be registered and logged in to get extension key.

Magento Connect 2.0

Magento Connect 2.0

RELEASE-0.6.1

  • [#471] Fixed addMessage() in messages block (@arosenhagen)
  • [#445] Update Cron.php for compatibility with MageWorx_XSitemap (@evensisftw)
  • [#474] Add ESI decoder utility (@jeroenvermeulen)
  • [#485] Trigger layout events when rendering ESI blocks (@eth8505)
  • [#490] Fix missing ESI blocks when they are defined in a reference instead
    of a block (@paales)
  • [#472] Added <only_cache_if> ESI parameter for caching flash message
    blocks (@jeroenvermeulen)
  • [#494] Added option to control the stripping of whitespace from generated
    VCLs (@eth8505)
  • [#549] Enabling the fix_product_toolbar option now clears previously set
    view preferences (@jeroenvermeulen)
  • [#529] Added decoding of the referrer to the ESI decoder
    utility (@jeroenvermeulen)
  • [#536] Allow // (double slash) comments in VCL files and strip them when
    trimming whitespace (@eth8505)

RELEASE-0.6.0

2014-03-03 22:45:25
  • Version number: 0.6.0
  • Stability: Stable
  • Compatibility: 1.6, 1.6.1, 1.6.2.0, 1.7, 1.8, 1.8.1, 1.11, 1.11.1, 1.12, 1.13, 1.13.1
You must be registered and logged in to get extension key.

Magento Connect 2.0

Magento Connect 2.0

RELEASE-0.6.0

This release requires a small addition to Varnish's configuration when used with
Magento CE 1.8+ or EE 1.13+, see these instructions

  • [#362] Fixed ESI detection for message block (thanks @eth8505)
  • [#380] Fixed ESI cache flushes not firing in some cases (thanks @gabrielsomoza)
  • [#391] Added Magento Composer Installer support (thanks @ajardin)
  • [#405] Fixed disabling Varnish bypass (thanks @ajardin)
  • [#438] Implemented ban lurker-friendly bans (thanks @jeroenvermeulen)
  • [#443] Fixed caching of static assets when the Add Store Code to Urls option
    is enabled (thanks @jeroenvermeulen)
  • [#345] Fixed compatibility with Magento CE 1.8 and EE 1.13
1 2 3 4 5 6
Reviews

About the Developer

This extension was developed by and is supported by nexcess_net

Rated 4.4 out of 5 by 23 reviewers.
Rated 1 out of 5 by Varnish & Turpentine when you have plenty of spare time After many and many hours decide to remove Varnish and Turpentine. Problems with shopping cart, ajax, geoip etc are not solvable if you aren't a super expert with loads of free and paid time. So leave it for the experts with to much free time. The removal of Varnish is easy, but after remove of turpentine hours and hours wasted time again to get things running again. August 2, 2015
Rated 4 out of 5 by Iphone Theme redering issue on some pages Overall this extension is working excellent.. Their is an issue with multiple theme rendering On my mobile iphone theme its sometime renders desktop theme.i have Normalize User-Agent enabled from admin And i have to keep flushing cache from admin to get mobile theme on particular page.. is there any solution? will really apreciate..!! February 24, 2015
Rated 5 out of 5 by When will this support Magento CE 1.9.. Great extension for Varnish but after testing it only works up to CE 1.7. I realise that magento has some significant changes in the later versions and hence this will not work with it correctly. Do you have any plans to implement support for CE 1.9? or do you have any fix we can apply as I am desperate to get it working! thanks December 20, 2014
Rated 4 out of 5 by It works perfect in 1.7.0.2 (multistore and multidomain) It works perfect in 1.7.0.2 (multistore and multidomain), after modifying the vcl to avoid the mistake of dirty cookie "double cookie frontend" If you solve the problem of double cookie, without needing to have to call our technicians, would be to give it a 5, for now I leave in 4 * January 31, 2014
Rated 4 out of 5 by Huge speed improvement but After finally getting it working, I noticed a massive speed increase on the website. But we are using 1.8.1.0 and found it has a problem with the cart. If you are using 1.8.0 or 1.8.1 don't use this yet until it has been updated. Or customers often wont be able to add items to the cart. January 29, 2014
Rated 5 out of 5 by Great speed improvement I got great speed improvement on my server using Varnish, it was a bit hard to set-up at the beginning but then I made it work. In the configuration backend port needs to be 8080 for Apache and Varnish needs to listen at port 80 in front. This is a sample configuration that works for me. Great piece of software for Magento ! October 28, 2013
Rated 5 out of 5 by Superb Varnish can be a real pain, particularly with ecom sites, but with a little nous this module works really really well, and we've seen massive page speed increases - particular on HA multi server environments. That said, if doesn't negate the need for some prior knowledge of varnish and your web server of choice. Big thanks to Nexcess for making it freely available! October 11, 2013
Rated 5 out of 5 by Turpentine - Varnish Cache - mature product. Today this is the only cache you can use to lower your server load to 0%. Easy install, easy to configure and maintain. No errors whatsoever. You need some magento layout knowledge to configure it with highly customized theme, but it works in 95% out of the box. August 12, 2013
Rated 5 out of 5 by Works great but... I'm not seeing any headers in the pages - does the extension remove them. Also the cart in the header is not updated when something is added - how do I fix this? August 7, 2013
Rated 5 out of 5 by why it happens? when i install it through magento connect manager, it returns: Checking dependencies of packages CONNECT ERROR: Unsupported resource type July 4, 2013
  • 2015-08-27T12:13:08.099-05:00
  • bvseo_lps, prod_bvrr, vn_prr_5.6
  • cp-1, bvpage1
  • co_hasreviews, tv_23, tr_23
  • loc_en_US, sid_14243, prod, sort_default
2 3 next>>
Q&A
(19 Questions : 16 Answers)

Product Q&A

Ask your questions. Share your answers.

 
 
« Back
 
 
Sort by
 
2 answers

1.8.1.0 Compatibility

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27347772
Customer avatar
Does this work with CE 1.8.1.0?
by
sml12
-
1 year, 8 months ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_404763
Customer avatar
Answer: 
From what I've gathered in my test environment, it is not. Looks like Varnish itself has some compatibility issues with 1.8.X and Turpentine goes right along with it. I can't get this working at all since the upgrade.
by
barproducts
-
1 year, 4 months ago
+1point
1out of 1found this answer helpful.
Was this helpful?Yes1No0

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27454397
Customer avatar
Answer: 
Version 0.6.0 upwards works with 1.8+. This version fixes an incompatibility with the form_key CSRF protection. You'll need to add -p esi_syntax=0x2 to your Varnish startup options.
by
multicoptersltd
-
1 year, 3 months ago
+1point
1out of 1found this answer helpful.
Was this helpful?Yes1No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_105580
Customer avatar
Does this extension work with Magento 1.9.0.1?
by
Kunzi
-
11 months ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_26873850
Customer avatar
Answer: 
BUMP! - Has this developer Varnished? lol.

When is an update available for 1.9.1 ?????
by
scribblevision
-
11 months ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_4899
Customer avatar
Answer: 
CE 1.9 is supported as of version 0.6.1
by
nexcess_net
-
10 months ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27588912
Customer avatar
Just wondered if this worked with V4 of varnish - it isnt mentioned on this page but it is talked about on your github?

Thanks
by
acarr
-
10 months ago
+1point
1out of 1found this question helpful.
Was this helpful?Yes1No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/magento-connect/skin/frontend/enterprise/connect/images/pictures/developer-avatar.jpg
Customer avatar
Answer: 
It seems that is not compatible :
https://github.com/nexcess/magento-turpentine/wiki/Installation
by
pydubreucq
-
1 month, 3 weeks ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0

Avatar Image Url:: http://www.magentocommerce.com/magento-connect/media/avatars/avatar_4899.png
Customer avatar
Answer: 
We're have an active development branch that supports Varnish 4, and should be adding official support for Varnish 4 in the coming weeks.
by
nexcess_net
-
4 weeks, 2 days ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_26234457
Customer avatar
After I enable Varnish and complete the install I am no longer able to view GET timthumb.php images for my homepage. Timthumb.php brings in several images for my slideshow and product slider. Anyone have any experience with getting timthumb.php images to work after enabling varnish on port 80 and setting up the turpentine plugin?

Cody
by
Betsworth22
-
2 years, 5 months ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_26268542
Customer avatar
Answer: 
Hi, im no expert but we managed to also install varnish and turpentine, the way i understand how it works is that varnish server is serving cached content. If timthumb.php serves dynamic images then varnish will show only the cached version. You have to create an xml block for that file. Then edit the turpentine_esi.xml and add that block with an esi parameter to tell varnish not to cache that block. When a the page is called, varnish will pull the block from the webserver and combine it with the cached version to serve the complete page. Hope this helps.
by
jpadua
-
2 years, 5 months ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_371050
Customer avatar
Hi, I don't know where and how to configure Varnish.
by
jaautomacao
-
2 years, 1 month ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27405268
Customer avatar
Answer: 
Hi,

After installation go to your Configuration panel.
( System > Configuration ).

In left panel there has to be a "Turpentine" option list. And in that list you can see Varnish and Caching options pages
by
semihmasat
-
1 year, 7 months ago
+1point
1out of 1found this answer helpful.
Was this helpful?Yes1No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_25933365
Customer avatar
HI,

How to solve this problem? On product click

ESI processing not enabled

Varnish 3
Magento 1.7.0.2
by
brunomenol
-
1 year ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/magento-connect/media/avatars/avatar_4899.png
Customer avatar
Answer: 
Apologies for the late response, then best place to ask questions about Turpentine is on the github:
https://github.com/nexcess/magento-turpentine

Please open an issue on github if this problem is still occurring and we'll see what we can do!
by
nexcess_net
-
4 weeks, 2 days ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_151175
Customer avatar
We are thinking of moving over to use this Varnish module instead of the one from Phoenix, but see the VCV file is being auto-generated.

We see it is possible to hook into the generated file with a custom file, however we need to add settings both in the top and in the end of the loading of the file. What are the recommendations here? Is it OK to just "fork" the generated file and just manually adjust that while file afterwards?
by
Trollweb
-
10 months ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/magento-connect/media/avatars/avatar_4899.png
Customer avatar
Answer: 
Apologies for the late response, then best place to ask questions about Turpentine is on the github:
https://github.com/nexcess/magento-turpentine

To answer your question, that should be ok. Just make sure that the Turpentine is not overwriting your customized VCL file when you save changes. You may also need to tweak your VCL file to take advantage of new features added to Turpentine.
by
nexcess_net
-
4 weeks, 2 days ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27408533
Customer avatar
How can i get the Authentication key for Varnish CLI access?

Also i faced some issues like
Error determining Varnish version: Varnish admin socket timeout
Failed to apply the VCL to 66.117.3.14:80: Failed to load configurator
Error determining Varnish version: Varnish admin socket timeout
Failed to load configurator

Please help us
by
gts_sandeep
-
9 months ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/magento-connect/media/avatars/avatar_4899.png
Customer avatar
Answer: 
Apologies for the late response, then best place to ask questions about Turpentine is on the github:
https://github.com/nexcess/magento-turpentine

To answer your question, the location of the authentication key is specified by the options given to Varnish when starting up - typically /etc/varnish/secret - but could vary depending on your server config.
by
nexcess_net
-
4 weeks, 2 days ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27335546
Customer avatar
Does this extension work with Magento 1.9.1?
by
efgenuss
-
6 months ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/magento-connect/media/avatars/avatar_4899.png
Customer avatar
Answer: 
Apologies for the late response, then best place to ask questions about Turpentine is on the github:
https://github.com/nexcess/magento-turpentine

To answer your question - yes, it does support CE 1.9.x
by
nexcess_net
-
4 weeks, 2 days ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27709416
Customer avatar
I followed the install instructions using modman and everything worked fine but I don't see any varnish configuration options showing up in my admin console.
by
nplatzkeii
-
6 months ago
0points
0out of 0found this question helpful.
Was this helpful?Yes0No0

Answers

Avatar Image Url:: http://www.magentocommerce.com/images/avatars/uploads/avatar_27709416
Customer avatar
Answer: 
No. It doesn't. It breaks the entire magento install. Awesome.
by
nplatzkeii
-
6 months ago
0points
0out of 0found this answer helpful.
Was this helpful?Yes0No0
  • 2015-08-27T12:17:15.902-05:00
  • bvseo_lps, prod_bvqa, vn_prr_5.6
  • cp-1, bvpage1
  • co_hasquestionsanswers
  • loc_en_US, sid_14243, prod, sort_default
2 next>>
  • 2015-08-27T12:17:15.941-05:00
  • bvseo_lps, prod_bvqa, vn_prr_5.6
  • cp-1, bvpage1
  • co_hasquestionsanswers
  • loc_en_US, sid_14243, prod, sort_default
2 next>>
Get Help

Support for This Extension

The best place to start if you need help with a specific extension is to contact the developer. All Magento developers have both a contact email and a support email listed.

Magento Platform Support

If you need support for a Magento platform, there are different options for support depending on which Magento platform you are using. Below are links for specific platforms.

In order to upload extension, you must be logged in to the Magento Community. Click here to login or register.

Close

Register

* Required Fields

Close window

Forgot Your Password?

Please enter your email below and we'll send you a new password.

* Required Fields

Close window

Login

To upload extension you must be logged in.

* Required Fields

Close window

You are using an outdated browser

We built Magento Connect using the latest techniques and technologies.
This makes Magento Connect faster and easier to use.
Unfortunately, your browser doesn't support those technologies.
Use the links below to download a new browser or upgrade your existing browser.