On Tuesday, July 12, 2005 8:33 AM [EDT], Stephen Turner <[EMAIL PROTECTED]> wrote:
> On Mon, 11 Jul 2005, Aengus wrote: >> >> CASE INSENSITIVE applies to the filename, and I, like you, would have >> assumed that it would apply to the arguments as well, but it doesn't >> appear to do so. > > The question of whether arguments are case insensitive is completely > independent of whether the stems are case insensitive. The former is a > property of the scripts running on the web server, the latter is (in > principle a property of the web server but in practice) a property of > the file system. > > Typically argument names come from web forms, so don't actually occur > in multiple cases. Argument values are a third question. Some of them > may be case sensitive and some case insensitive, depending on the > interpretation of each argument. Anyway, I'm certainly not going to > fold them all to lower case just because the file system is case > insensitive. I should have made it clearer in my original response that you can't make the same assumptions about case sensitivity for arguments as you can make for filenames. Having said that, it seems reasonable that there should be a ARGSCASE INSENSITIVE command, just as there is a USERCASE INSENSITIVE, for cases where, due to different styles used by differernt page authors, for example, you end up with mixed case arguments where the case has no significance. It might also be a useful addition to the documentation to add the clarification that cASE INSENSITIVE applies only to the filename part of URLs, not to the arguments. Aengus +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
