in reply to Re: Meaning of part of a URL
in thread Meaning of part of a URL

You don't actually need the ? as "extra" data will be passed in the PATH_INFO environment var and can be retrieved and used by a CGI quite easily from there. ?& is something of a contradiction in terms although I guess most CGI parsing libs would deal with it and discard the first nameless, valueless param.

Replies are listed 'Best First'.
Re^3: Meaning of part of a URL
by CountZero (Bishop) on Jun 24, 2008 at 19:21 UTC
    You are right, but strictly speaking it is then not a parameter of the GET call and your server must "know" that some of the info is in the path and not in the parameter list.

    Try to drop the '?' in the above perlmonks URL and see what I mean.

    I wonder, is '&' even allowed as part of a path?

    CountZero

    A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James