Arunima76
asked on
CGI/FastCGI links
I need links to tutorials for CGI and FastCGI. The ones i find just explain GET/POST and nothing more.
Any recommended book on these topics?
Thanks.
Any recommended book on these topics?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
sorry, I don't know what "good tutorials" are in your mind :-)
simple STFW and you'll find tons of them ...
I'd start here: http://www.w3.org/CGI/
simple STFW and you'll find tons of them ...
I'd start here: http://www.w3.org/CGI/
ASKER
Well! I mentioned in my first post "The ones i find just explain GET/POST and nothing more." And i guess CGI cant be just GET/POST.
I thought that somebody outthere might be aware of more informative tutorials.
Anyways, thanks for your help.
I thought that somebody outthere might be aware of more informative tutorials.
Anyways, thanks for your help.
if you look at w3c's docs, you'll see that GET should be used for insensitive informations while POST for more sensitive informations.
Meanwhile, roughly 8 years after publishing these standards, the web and its usage has changed, and though the techniques used to penetrate applications. To destinguist GET and POST according sensitive informations does no longer make sense, 'cause it's just one step more to penetrate and/or automate POST requests.
The main advantage of POST might be that the amount of data is not limited to 1k (as standard says, 2k on most servers, 8k commonly used) as it is for GET.
The disadvantage of POST is that a lot of security mechanisms do not check POST parameters, and some programers of web applications do either (means they don't care if GET or POST was used).
Hope this helps a bit more.
Meanwhile, roughly 8 years after publishing these standards, the web and its usage has changed, and though the techniques used to penetrate applications. To destinguist GET and POST according sensitive informations does no longer make sense, 'cause it's just one step more to penetrate and/or automate POST requests.
The main advantage of POST might be that the amount of data is not limited to 1k (as standard says, 2k on most servers, 8k commonly used) as it is for GET.
The disadvantage of POST is that a lot of security mechanisms do not check POST parameters, and some programers of web applications do either (means they don't care if GET or POST was used).
Hope this helps a bit more.
ASKER
Thanks.
ASKER
Can u direct me to some places where i can find good CGI tutorials...??