Re^3: How to convert an @ARGV to form based input?

But I don't want the web clients location: to see, or be able to manipulate the query string -- hence the desire to put the form fields within the script itself, and my choice of using the POST method.

Yeah, POST doesn't hide anything from the client

Comment on Re^3: How to convert an @ARGV to form based input?

Replies are listed 'Best First'.
Re^4: How to convert an @ARGV to form based input? by taint (Chaplain) on Aug 21, 2012 at 09:10 UTC
No? I've got a whois form that is accessed by way of: `http://whois.mydomain.tld/` and no matter what you put into the location field of your browser after the /, you'll be returned with `http://whois.mydomain.tld/` in your location: bar, and an empty form, waiting for you to place a Domain name, IP address, AS number, or RP into the field. The location bar never reveals the query, and can't be manipulated. So I'd have to respectfully disagree with your assertion. --Chris #!/usr/bin/perl -Tw use perl::always; my $perl_version = "5.12.4"; print $perl_version;	[reply] [d/l] [select]
Re^5: How to convert an @ARGV to form based input? by aaron_baugher (Curate) on Aug 21, 2012 at 09:55 UTC
Everything that your browser sends to a web server can be manipulated. Using POST instead of GET just means it doesn't show in the location bar, which makes it slightly more difficult than simply editing the URL. Aaron B. Available for small or large Perl jobs; see my home node.	[reply]
Re^5: How to convert an @ARGV to form based input? by Anonymous Monk on Aug 21, 2012 at 09:39 UTC
The location bar never reveals the query, and can't be manipulated. I did not mention the location bar :) The location bar is irrelevant . The HTML can be manipulated. The HTTP can be manipulated. POST changes nothing.	[reply]