Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having a hard time coming up with a use case in which case-sensitive min/max parameters make sense and several solid cases for a case-insensitive min/max.


With case insensitive min/max:

an exact match on /users could be accomplished with min=john&max=john

Currently, for this case, min=john&max=JOHN seems to work, but it is possible for other values to sneak in there requiring a client side post filter.

Discussed on and and

share|improve this question
Yeah, they really shouldn't be case sensitive. Fixing... – Kevin Montrose Jul 9 '10 at 2:16
up vote 1 down vote accepted


Observe, as I filter out all the Jons, Johns, and Jon Skeets in the system.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .