[Dancer-users] case insensitive param keys

[damien krotkine]

On 6 October 2010 19:18, Stephane <stephane at shimaore.net> wrote:

> 1. What does the RFC(s) say?
>>
>
> I suspect this is (one of) the reference:
>
> http://www.w3.org/TR/1999/REC-html401-19991224/interact/forms.html#h-17.13.3.4
>
> (I'd expect things like case-sensitivity(?) to be framework decision rather
> than a protocol / specification decision, though.)
>
>
>  2. How are other frameworks handling it?
>>
>
> CGI.pm is case-sensitive ;)
>
>
>  Without spending a lot more time researching, it would seem like the
>> correct
>> approach is:
>> 1) case sensitive by default
>> 2) case insensitive by config
>>
>
> Agreed.
>
> I was going to suggest that the "params_lc" option (mentioned earlier)
> could be a boolean or a CODE ref so that people can do fancy transforms
> (including locale-dependent ones) if they'd like.


In this case, "params_lc" would be a bad name. What about
"params_normalization" or something similar, that can accept either
'uppercase', 'lowercase', or a code reference?

Also, some people may want to normalize the params only in some part of the
application. Do we want to handle that ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.backup-manager.org/pipermail/dancer-users/attachments/20101007/89bb8e37/attachment.htm>