Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

Re: Direct access to client socket in CGI/mod_perl?

by DapperDan (Pilgrim)
on Nov 28, 2002 at 21:24 UTC ( #216384=note: print w/ replies, xml ) Need Help??


in reply to Direct access to client socket in CGI/mod_perl?

In a cgi environment such as that created by Apache's mod_cgi, the only real difference between a POST request and a PUT request is the contents of $ENV{REQUEST_METHOD}. Do a PUT and a POST request to /cgi-bin/printenv.pl (in a stock Apache deployment) and diff the responses to see what I mean.

merlyn has already said that mod_cgi gives you a live connection to the socket, so you just read from STDIN in your CGI program as you would normally. People almost always want decoded form/url-encoded name/value pairs so you will see them use CGI.pm, but there is technically nothing to stop you reading STDIN directly. I use this in CGI programs that support machine/non-human HTTP clients, which POST and PUT XML and YAML in the body of the request, rather than the usual form data. (The contents of the Content-type: header change to "text/xml" or whatever to reflect this, obviously.)

HTH, HAND.


Comment on Re: Direct access to client socket in CGI/mod_perl?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://216384]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (11)
As of 2015-07-31 00:43 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (274 votes), past polls