Oh I see, right, it matches against the whole concatenated hash string. Why is it that this purges all files from w0011.example.com
purge.hash w0011.*#.* But this does nothing? purge.hash w0011.*#.*# Flipping the #'s around works: purge.hash #w0011.*#.* This also has no effect, is "+" not supported in the regex? purge.hash w0011.+#.+ purge.hash w0011.+#.+# purge.hash #w0011.+#.+ But none of these do anything: purge.hash #w0011.*#.*html purge.hash w0011.*#.*html purge.hash w0011.*#.*html# So I'm somewhat confused again. I haven't messed with vcl_hash at all. Thanks, Skye On 14-Jul-08, at 12:33 PM, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Skye Poier > Nott writes > : >> Updated to r2945 today, is purge.hash changed or broken? >> >> This works: >> >> purge.url . >> purge.hash . >> >> But none of these have any effect: >> >> purge.hash .#.# > > This would only purge single character urls on single character > host names. > > Try: > purge.hash .*#.*# > > for wider matching > >> (The last trunk rev I was using had #host#path but now it's >> host#path# ? It would be nice if 'help purge.hash' mentioned the >> current expected format) > > The expected format is what vcl_hash {} set up, and since the > user can redefine that function, a constant help message would > have good chances of being confusing. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by > incompetence. > _______________________________________________ > varnish-misc mailing list > varnish-misc@projects.linpro.no > http://projects.linpro.no/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc