in reply to CGI POST vs. GET problem

How are you URL encoding the get? I believe the latest versions of CGI use ; to seperate parameters instead of & unless you specificially tell it other wise. Checking the $ENV{QUERY_STING}and GET access as stated above are both two things you should check.

-Lee

"To be civilized is to deny one's nature."

Replies are listed 'Best First'.
Re: Re: CGI POST vs. GET problem
by Xxaxx (Monk) on Jun 06, 2001 at 13:06 UTC
    Looking in the version of CGI.pm that I have on my server, it shows the following: 
    sub parse_params {
    my($self,$tosplit) = @_;
    my(@pairs) = split(/[&;]/,$tosplit);
    my($param,$value);
   etc.

    [download]
    The use of the & or ; in the split should mean that CGI will work for browsers using & to separate pairs as well as working for browsers using ; to separate pairs.

    Claude

[reply]
[d/l]
      I'd look to make sure you are getting passed the QUERY_STRING.

      Then I would look at the server config to make sure GET is enabled.

      -Lee

      "To be civilized is to deny one's nature."
[reply]

In Section Seekers of Perl Wisdom