6

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.

Example:

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 Finding a user given their (exact) display name and https://stackapps.com/questions/1041 and

1
  • Yeah, they really shouldn't be case sensitive. Fixing... Commented Jul 9, 2010 at 2:16

1 Answer 1

1

Done.

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

0

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.