Closed marcosdemasi closed 9 years ago
Did you resolve this? I have a similar issue I am struggling to resolve.
Hi, prysie. Try to disable/clean cache and then run Turpentine again.
I hope this helps
Hi - thanks for responding, I have reapplied Vcl and cleared cache many times, but it does not seem to help my issue. My esi blocks are been injected as URLs within the page element but instead of redirecting it is putting the message 'this is permanently moved to here' clicking on the here displays the right content - I'm not 100% my turpentine_esi.xml is setup to handle all my custom theme elements but I'd still expect the basics like the footer block to work. Anyway thanks for responding I have found a wealth of knowledge in people's comments in this and other forums.
@prysie Can you post your log? Also, it's generally a better idea to put any ESI policy changes into a local.xml file to avoid losing any changes when you update the extension.
@aricwatson I will apply your new release this weekend and try this all again, if I still have issues I will post the logs etc here
Thanks!
Closing for lack of feedback.
I'm seeing this exact same issue after installing turpentine for the first time. The blocks I expect to be replaced by esi show the message: "Moved Permanently The document has moved here. Apache/2.4.10 (Linux/SUSE) Server at www.domain.com Port 80" Where 'here' contains a link to the controller action to render the esi block, example: http://www.domain.com/turpentine/esi/getBlock/method/esi/access/private/ttl/18000/hmac/62f23c55a6952914297c2d172d35a945ffb54b0c542d1f5c9bd726394dec1bae/data/RaMIDT0wgiLyO5TXtXPiri2ytSGVn2hD-Ue6t9krZTVjhiU-...
I haven't added any xml changes, I am only using the turpentine_esi.xml that was provided. No modifications have been made yet. Using Magento EE 1.14.1.0 Have flushed cache, restarted varnish many times without change Any idea what I am doing wrong? Thanks
It sounds like some sort of a redirect is occurring at the apache level. Is there anything that seems to be related in your logs? What version of Varnish?
Hi, Thanks for the reply. Varnish version 3.0.5 I found the problem. You are correct, it was an apache level redirect in an .htaccess rule I had setup for redirecting all url's with a trailing slash to urls without. When I added an exclusion to this rule for the turpentine route, this problem stopped. Everything looks much better now, thanks!
Can you post the exclusion rule configuration here? It would help me out thanks :)
Closing for now, but feel free to reply if we can still help out.
I am using Magento ver. 1.9.1 and Varnish 4.0.2 and code from https://github.com/nexcess/magento-turpentine/pull/541 I enabled the logs and realised that despite turpentine_esi.xml file is correct, there is no injections nether ESI blocks is been created. The strange thing is that is was working fine until I create an AMI image (on AWS) and used it to create a new machine.
Any, suggestion, comment, help is welcomed:
Follows is
See result for varnish -b command: varnish -b
And the default.vcl file: