Hey, been messin with this a bit... it's the night of the CGI
variable, apparently.
John, I can get the XML data back this way:
temp.cfm
-----------------------------
<cffile action="READ" file="#expandPath('.')#\bookmarks2.xml" variable="myXML">
<cfhttp url="http://w2ksrv1/tmp/test2.cfm"; method="post" result="myHttp">
<cfhttpparam name="cXML" value="#urlEncodedFormat(myXML)#"
type="HEADER">
</cfhttp>
<cfdump var="#urlDecode(myHttp.fileContent)#" />
test2.cfm
-----------------------------
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Untitled</title>
</head>
<body>
<cfdump var="#cgi.cXML#" />
</body>
</html>
Is it possible you're getting the CGI and Request scopes mixed up? The
XML file gets sent as an HTTP header, and those stay encapsulated in
the CGI scope. They don't, however, show up in a CFDUMP of the CGI
scope... which I eventually had to look up in the help files.
Apparently, it's that way "by design." It DOES however show up when
you call it directly (i.e. cgi.cXML).
It's the only way I can see doing what you want without having some
sort of a bridge between the CGI and Request scopes.
Hope that helps,
J
On Wed, 02 Mar 2005 23:23:46 -0500, John Farrar
<[EMAIL PROTECTED]> wrote:
> Roland,
>
> When I read content coming from the Ariba middle connection server it is
> done like this in our live site code...
>
> <cfscript>
> myCXML = XMLParse(request.HTTPHeader.content);
> ...
> ...
> ...
>
> I may try doing what you are saying from our Ariba test system. It has
> been months since I dove in... and at this point the why or how that
> variable was figured out to work is beyond me. It was when we were
> learning how to do it the first time.
>
> John
>
> An archive of the CFCDev list is available at
> www.mail-archive.com/[email protected]
>
>
--
Continuum Media Group LLC
Burnsville, MN 55337
http://www.web-relevant.com
http://cfobjective.neo.servequake.com
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
