Peter M. Jansson wrote: > Usually, POST content contains query parameters, which can be accessed as > members of the ns_set returned from ns_getform. Are you POSTing something > that isn't a query parameter? If so, can you redo things so that you post > it as a query parameter? (That's the easiest thing, then you can just do > ns_getform and pick out the proper member of the resulting ns_set.)
Yes, I realize that POST content contains query parameters, but in this case, I'm posting a SOAP message, so I need to access the POST content to get the envelope data. Reformatting is not an option. The soap messages have the following format: POST /axis/servlet/AxisServlet HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.0 Host: localhost Cache-Control: no-cache Pragma: no-cache SOAPAction: "http://soapinterop.org/"; Content-Length: 469 <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <ns1:echoString soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:ns1="http://soapinterop.org/";> <inputString xsi:type="xsd:string">abccdefg</inputString> </ns1:echoString> </soapenv:Body> </soapenv:Envelope> > On Sun, 13 Oct 2002, Dan Wickstrom wrote: > > >>I would like to access the content associated with a POST, and so far, >>the only method I can see to do this is something like the following: >> >> >> >> set filename [ns_mktemp /tmp/fooXXXXXX] >> set fh [open $filename w] >> ns_writecontent $fh >> close $fh >> set fh [open $filename r] >> set content [read $fh] >> close $fh >> ns_unlink -nocomplain $filename >> >> >>I would like to be able to do this without having to use a file as an >>intermediary. Something like the following: >> >> set content [ns_conn content] >> >>Looking in conn.c, I've noticed that ns_conn seems to have had a content >>sub-command in the past, but it's no longer implemented. >> >>Regards, >> >>Dan >> > >
