-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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.
It seems to me that one usable approach would be to require the "?" query string to be an explicit part of rule, if it's expected to be matched against query strings. So "-A .htm,.gif,*Action=edit*" would all result in matches against the filename portion only, but "-A '\?*Action=edit*' would look for "Action=edit" within the query-string portion. (The '\?' is necessary because otherwise '?' is a wildcard character; [?] would also work.) The disadvantage of that technique is that it's harder to specify that a given string should be checked _anywhere_, regardless of whether it falls in the filename or query-string portion; but I can't think offhand of any realistic cases where that's actually useful. We could also supply a --match-queries option to turn on matching of wildcard rules for anywhere (non-wildcard suffix rules should still match only at the end of the filename portion). Another option is to use a separate "-A"-like option that does what -A does for filenames, but matches against query strings. I like this idea somewhat less. Thoughts? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. GNU Maintainer: wget, screen, teseq http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIyrXz7M8hyUobTrERAk+5AJ0ckiE4+bEMEFe9aD8bBNY3HH+IZACdERCs wab0TyBLCbW/6DYm+8gAExM= =pwb/ -----END PGP SIGNATURE-----
