Blocks not showing - wrong src?

Thanks for the great extension,

just trying to make it work with one project (with varnish). In this project I have one webserver with ez publish and a separate varnish server.

First the var/si-blocks/---.html files are being created ok.

The main problem is that the blocks are not being showed, perhaps because the src includes is like:

Thanks Jérôme for the fast answer... Now I really now how to proceed with my project...

Hi Pablo,

not sure I understand your question but I'll try to answer :)

Thanks Jérome.

I damned, I copy/paste your doc... please change the "tll" to "ttl" in the example ... ###!:p
there :
{si-block key=string $key [tll=integer $ttl]}

Hi,

I do not think it is a problem to have relative path in your ESI src="" attribute. As long as the file is accessible directly by your browser it should be fetched by Varnish as well. If for example, from your browser you can access http://example.com/./path/../to/../file.html then Varnish should be able to access the file as well.

Indeed it may be..

As defined in ESI specs :

Relative URIs will be resolved relative to the template.

eZ Publish handles url aliases but as all requests are managed on web root (via index.php redirection), the real interpretation path remains "/".
But for Varnish, a slash in url constitutes a new "subfolder" that makes it a new home to be relative to.

Then when you play with pathes deeper than one level, the created esi request will be erraneous as it considers the last slash as a basis path.
For an ESI block called from a page named "http://example.com/Folder/Subfolder/The-final-content", that kind of uri will be produced : http://example.com/Folder/Subfolder/var/si-blocks/file.htm , which won't be a valid one.

Possible workarounds I see :
- Hack the FS handler in ezsiblockfunction.php to make the generated "src" absolute from "/" (Valentin's solution)
- Add an Apache rewrite rule to strip the folder path from the ESI request, rewriting them relative to "/" (not very smart..)
- Add a dedicated rule in Varnish VCL, to reconsider the base path before parsing esi tags :
# Parsing ESI tags
set bereq.url = "/";
esi;

But currently it doesn't seem to me possible to use the FS handler in a host configuration context without one of those workarounds?

And right with mod_deflate, I've also lost a few hairs with it... thanks Pablo to point it!