As stated earlier you can use telnet/nc. There may be a better option for what you're attempting. For example, have you tried changing the TTL of your objects? It's possible to avoid purges altogether.<div><br><div class="gmail_quote">
On Thu, Mar 14, 2013 at 11:27 AM, Souvik Bhattacharya <span dir="ltr"><<a href="mailto:souvikbhattacharyas@gmail.com" target="_blank">souvikbhattacharyas@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> That means, whenever I need to request for "PURGE" I need to fire the Url by my self through container. Then it will be a extra round trip of client to server. Is there anyway to avoid that<div>
<br><br><div class="gmail_quote">
On Thu, Mar 14, 2013 at 10:14 PM, 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>> a) As per the guide line when I will write 'purge' content management<br>
> system send a special HTTP request to Varnish. So, is this request sending<br>
> done automatically or my own program need to send a request with<br>
> request.method ='PURGE'<br>
<br>
</div>Whether the request is done automatically or not depends on the CMS. I assume<br>
the CMS has built in functionality to make the request. You'll need to read<br>
the documentation that came with the CMS to determine how it's handled.<br>
Assume it's done for you though.<br>
<div><br>
> b) In the below program to purge a object VCL check is the request is with<br>
> 'PURGE'. But if I am initiating purge for the first time then how the<br>
> req.request will be 'PURGE'?<br>
<br>
</div>You can simulate a purge by sending the following bytes to varnish:<br>
<br>
PURGE /url HTTP/1.0<br>
<br>
You can send this via telnet, or a programming language of your choice, but<br>
ultimately this is how request.method gets set to 'PURGE'.<br>
<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>
</blockquote></div><br><br clear="all"><br></div><div><div>-- <br>Thanks & Regards,<br><br>Souvik Bhattacharya
</div></div><br>_______________________________________________<br>
varnish-misc mailing list<br>
<a href="mailto:varnish-misc@varnish-cache.org" target="_blank">varnish-misc@varnish-cache.org</a><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a><br></blockquote></div><br>
</div>