No subject

application, then you can do this yourself, but if you have links coming in
from external sites, and someone chooses to link to your site as

 http://www.example.com/?MyPaRAM=Whatever

then simple code in Dancer expecting to see params->{myparam} will silently
fail.  Is this intentional behavior that I need to code around in my app, or
something that could be fixed in Dancer::Request?

Thanks in advance,

Mike.


PS: Does anyone know of a good way to search the archives for this list
other than using a site: param on google?

--0016e65684be84fe7f0491f36500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>When Dancer::Request::_parse_get_params() parses the QUERY_STRING (as =
I assume the post body), it leaves the key names in whatever case they come=
 in as. =A0I checked some RFCs (<a href=3D"http://tools.ietf.org/html/rfc39=
86#section-6.2.3">http://tools.ietf.org/html/rfc3986#section-6.2.3</a>) to =
see if there was anything definitive, but not really that I could find.</di=
v>
<div><br></div><div>From a pragmatic perspective, it would be nice to have =
the keys forced to lowercase by Dancer::Request. =A0If you control every li=
nk to your application, then you can do this yourself, but if you have link=
s coming in from external sites, and someone chooses to link to your site a=
s</div>
<div><br></div><div>=A0<a href=3D"http://www.example.com/?MyPaRAM=3DWhateve=
r">http://www.example.com/?MyPaRAM=3DWhatever</a></div><div><br></div><div>=
then simple code in Dancer expecting to see params-&gt;{myparam} will silen=
tly fail. =A0Is this intentional behavior that I need to code around in my =
app, or something that could be fixed in Dancer::Request?</div>
<div><br></div><div>Thanks in advance,</div><div><br></div><div>Mike.</div>=
<div><br></div><div><br></div><div>PS: Does anyone know of a good way to se=
arch the archives for this list other than using a site: param on google?</=
div>
<div><br></div><br clear=3D"all"><br>

--0016e65684be84fe7f0491f36500--