might I trigger
this to happen without modifying the backend CGI? ie is it possible to
make an nginx location which can trigger fastcgi_cache_purge on any POST
request?
Thanks for any thoughts
Ed W
___
nginx mailing list
nginx@nginx.org
http
)(?/.*)?$ {
Of course it still depends on someone's preference what to match in
case of
/foo.php/bar.php/quux
-cs
You beat me - I was just about to post the same!
I think the non greedy is probably the more common case
Thanks!
Ed W
___
nginx mailing
127.0.0.1:9000;
}
Thanks!!
Can I ask you to confirm the correction of a typo in your answer. Do I
want this:
(?.*) {
ie is this ammended version correct in the face of a URL such as:
blah.php/some/path?param=2
Thanks
Ed W
xists? Also, why does uncommenting the return 404 cause some kind of
breakage (not even sure I understand exactly what happens? Seems like
the paths get broken?)
Thanks for any help?
Ed W
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/ma
