accept/reject rules based on querysting

Any ideas about when this option (or an acceptable workaround) will be implemented ? I need to include/exclude based on querysting (with regular expression of course). File name is not enough. Thanks. __ Correo Yahoo! Espacio para todos

accept/reject rules based on querysting

Any ideas about when this option (or an acceptable workaround) will be implemented ? I need to include/exclude based on querysting (with regular expression of course). File name is not enough. Thanks. __ Correo Yahoo! Espacio para todos tus

Re: accept/reject rules based on querysting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gustavo Ayala wrote: Any ideas about when this option (or an acceptable workaround) will be implemented ? I need to include/exclude based on querysting (with regular expression of course). File name is not enough. I consider it an important

Re: A/R matching against query strings

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I sent the following last month but didn't get any feedback. I'm trying one more time. :) - -M Micah Cowan wrote: On expanding current URI acc/rej matches to allow matching against query strings, I've been considering how we might enable/disable

RE: A/R matching against query strings

Micah Cowan wrote: On expanding current URI acc/rej matches to allow matching against query strings, I've been considering how we might enable/disable this functionality, with an eye toward backwards compatibility. What about something like --match-type=TYPE (with accepted values of all,

Re: A/R matching against query strings

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony Lewis wrote: Micah Cowan wrote: On expanding current URI acc/rej matches to allow matching against query strings, I've been considering how we might enable/disable this functionality, with an eye toward backwards compatibility. What