Re^4: Unwanted parameter when executing CGI scripts

Thank you very much for your answer, but I just haven't got it yet. Please forgive me if I'm too stupid, but I think you are testing if the query string's length is >0, and your code only gets executed if this condition is true.

But when calling the script without any parameters, the length of the query string is 0, and that evaluates to false, so the whole line doesn't get executed.

Please correct me if I am wrong.

Regards,

Nocturnus

Comment on Re^4: Unwanted parameter when executing CGI scripts

Replies are listed 'Best First'.
Re^5: Unwanted parameter when executing CGI scripts by tobyink (Canon) on Jan 05, 2013 at 23:08 UTC
Indeed, the whole line doesn't get executed. But the line doesn't need to be executed because there's no query string. Thus there will be no keywords; nothing to clean up; no work needs to be done. `perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'`	[reply]
Re^6: Unwanted parameter when executing CGI scripts by Nocturnus (Scribe) on Jan 07, 2013 at 08:07 UTC
But that was exactly my problem: If I called `/cgi-bin/script.pl` (i.e. without any parameters and without query string), CGI.pm behaved like if I had called `/cgi-bin/script.pl?keywords=` I should have mentioned that my application in this case needed to get the parameters from the query string only (GET parameters) and that it should not get the POST parameters. Thus, I was using `$q -> url_params` instead of `$q -> param` Perhaps that's the reason for the misbehavior. Furthermore, I have seen some more misbehavior (see post below), so I dumped CGI.pm; I am now parsing the query string myself. Regards, Nocturnus	[reply] [d/l] [select]