hi i'm seeing some weird behavior passing args in mason, so i'm fishing for theories.
a particular GET is issued featuring a URL with a long URI encoded parameter: /cgi/script.pl?alt=n&opt=0&misc=7.1240377213708&id=351845849¶m=627934&giant=Andy%3d2%26Betty%3d5%26Carol%3d1%26David%3d1795%26Ellen%3d511%26Frank%3d1152%26Gilbert%3d864%26Horace%3d400%26Ingrid%3d300%26Josephine%3d86%26Killer%3dLyle%20Martha%26Neville%3d589855%26Owen%3d524288%26Peter%3d589827%26Quincy%3d3%26Rory%3dhttp%3d127%2e0%2e0%2e1%3a8888%3bhttps%3d127%2e0%2e0%2e1%3a8888%3b when i look in the access log, i see it plain as day. but when this code is executed in the script: warn '%ARGS', "\n", Data::Dumper::Dumper ( \%ARGS ); i don't see the 'giant' name value pair in the output. all the other params are there. why is this? -- \js oblique strategy: the most important thing is the thing most easily forgotten ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
