in reply to Re^3: Calling a radio button to the second cgi script
in thread Calling a radio button to the second cgi script

If you can get access to the server logs you can see what's values are being sent to the server

No you can't, servers don't log that stuff unless you add it yourself, and its mostly a waste of space

  • Comment on Re^4: Calling a radio button to the second cgi script

Replies are listed 'Best First'.
Re^5: Calling a radio button to the second cgi script
by bitingduck (Deacon) on Jun 12, 2012 at 07:07 UTC

    My hosting server logs include all the parameter lists in the requested URLs by default. It doesn't take that much space.

    Update: The default apache install on OS X will also show the parameter list in the log if you change the POST to a GET. You don't want to leave it that way, but it can be useful for debugging. It indeed sends only one word values, as pointed out in several replies now.

[reply]

      My hosting server logs include all the parameter lists in the requested URLs by default. It doesn't take that much space.

      Update: The default apache install on OS X will also show the parameter list in the log if you change the POST to a GET. You don't want to leave it that way, but it can be useful for debugging. It indeed sends only one word values, as pointed out in several replies now.

      Sounds like a lot of wasted physical and mental effort

      The OP has perl cgi program that compiles and runs -- time to stop fooling around with webserver configuration and logfiles and start debugging the application.

      Simply call DebugCGI and read the webpage

[reply]
        tail -f /var/log/apache2/access_log

        [download]

        And you can watch what the webserver is receiving. Hardly effort, and often useful.

[reply]
[d/l]

In Section Seekers of Perl Wisdom