Understood.<br><br>any possibility of storing the header sent by esi processed script (abc.php) into a temparoty variable and then including it to response from vcl_deliver?<br><br><div class="gmail_quote">On Sat, Oct 13, 2012 at 11:35 AM, Paul A. Procacci <span dir="ltr"><<a href="mailto:pprocacci@datapipe.com" target="_blank">pprocacci@datapipe.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Sat, Oct 13, 2012 at 11:20:24AM +0530, linuxsupport wrote:<br>
> I think I did not make it very clear, let me explain<br>
> I have a file named abc.html as below<br>
> <html><br>
> <head><br>
> <title>Test</title?<br>
> <body><br>
> <p>Test Page</p><br>
> <p><esi:include src="/cgi-bin/abc.php"/></p><br>
> </body><br>
> </html><br>
> This abc.php sends cookie, what I want is to cache all the contents of<br>
> abc.html and when doing esi processing (abc.php) include the Set-Cookie<br>
> header sent by abc.php with the response.<br>
> right now, abc.html is being cached and esi processing for abc.php is<br>
> also working but Set-Cookie header sent by abc.php is not being sent to<br>
> client.<br>
> possible?<br>
<br>
</div>See chapter six of the ESI spec: <a href="http://www.w3.org/TR/esi-lang" target="_blank">http://www.w3.org/TR/esi-lang</a><br>
<br>
When an ESI template is processed, a separate request will need to be made for each include encountered. Implementations may use the original request's headers (e.g., Cookie, User-Agent, etc.) when doing so. Additionally, response headers from fragments (e.g., Set-Cookie, Server, Cache-Control, Last-Modified) may be ignored, and should not influence the assembled page.<br>
<br>
Given the above, and given your explanation of your app disgarding cookies, then I'm going to go out on a limb and say i`not possible`.<br>
<div class="HOEnZb"><div class="h5"><br>
~Paul<br>
<br>
________________________________<br>
<br>
This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See <a href="http://www.datapipe.com/legal/email_disclaimer/" target="_blank">http://www.datapipe.com/legal/email_disclaimer/</a> for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you.<br>
</div></div></blockquote></div><br>