You could just go into the services and check the box that says "Allow
desktop interaction"

I think that might solve your problem.

______________________
steve oliver
atnet solutions, inc.
http://www.atnetsolutions.com


-----Original Message-----
From: Ron Davis [mailto:[EMAIL PROTECTED]] 
Sent: Friday, February 15, 2002 7:30 PM
To: CF-Talk
Subject: RE: CFHTTP construction? Fix??


After my last post, I did a bit of digging and found this:

http://www1.oli.tudelft.nl/docs/Developing_Web_Applications_with_ColdFus
ion
/15_Interacting_with_Remote_Servers/dwa15_06.htm

here is an excerpt:

CFHTTP uses the InetSDK to conduct all HTTP and HTTPS transactions and 
relies on the WinInet DLL and Schannel DLL for its SSL implementation.
The 
WinInet bug constrains storage of SSL certificate information to the
user 
level. This means that WinInet does not interrogate the registry for 
certificate information if the client that loads the DLL is a service.
As 
a result, a CFHTTP request to an https:// url, will fail if ColdFusion
is 
running as a service.

Soooo.... does that mean I'll have to re-arrange how CF runs?? (the 
workaround is described in the article)... seems like there are a lot of

downsides to this and I would love to find out what everyone else 
thinks... 

Thanks again all

-Ron

>>> [EMAIL PROTECTED] 02/15/02 07:25PM >>>
One last question... Would it matter that I'm doing the GET on an HTTPS 
server and not an HTTP server?

????

Thanks!

-Ron

>>> [EMAIL PROTECTED] 02/15/02 07:22PM >>>
Well.. .that solved my problem, more or less... =)  Now, instead of 
getting an error, I just get my page returned, but the GET operation 
doesnt return anything... I was told that if it was sent out
successfully,
 
it would return a formatted web page with hidden form fields in it.  
But, 
where the information is *supposed* to be inserted, its just blank..?  
Like nothing came back.. or nothing was sent?

Thanks again!!

-Ron

>>> [EMAIL PROTECTED] 02/15/02 06:43PM >>>
> Every time I run this code I get an error saying :
> 
> CFHTTP
> Incorrect number of columns in row.
> 
> <CFHTTP 
> URL="https://webapp/PayMe/L3/Receipt/pgReceiptVerification?mercha 
> nt_id=#session.merchant_id#&PayMe_Transaction_Id=#session.PayM
> e_Transac
> tion_Id#&Request_Type=RECIEPT"
> METHOD="GET"
> PORT="443"
> NAME="MyTransaction"
> RESOLVEURL="false"
> THROWONERROR="yes"
> COLUMNS="Merchant_Id, PayMe_Transaction_id, Request_Type, 
> Transaction_Sta
> tus">
> 
> <CFHTTPPARAM TYPE="URL" NAME="Merchant_Id" VALUE=#url.Merchant_Id#>



> <CFHTTPPARAM TYPE="URL" NAME="PayMe_Transaction_id" VALUE=#url.PayM


e_
> Transaction_Id#>
> <CFHTTPPARAM TYPE="URL" NAME="Request_Type" VALUE="RECEIPT">
> 
> </CFHTTP>

That's because you're giving your CFHTTP tag a NAME attribute. When you
do
this, CFHTTP expects to retrieve a text file formatted a certain way,
such
as comma-delimited text. If the file is formatted properly, it would 
create
a query object that you could then reference like this:

<cfoutput query="MyTransaction">

> Do I need the CFHTTPPARAM's here? (I'm not familiar with them either, 
> obviously)... Can anyone see anything wrong with the above code?

No, you don't need them. I'm surprised they don't cause an error. It 
was 
my
understanding that, in prior versions of CF at least, you couldn't use
CFHTTPPARAM without using METHOD="POST" in your CFHTTP tag. I could 
be 
wrong
about that in CF 5, though. In any case, you don't need them here
because
you're embedding the data in the URL attribute of your CFHTTP tag.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/ 
voice: (202) 797-5496
fax: (202) 797-5444




______________________________________________________________________
Dedicated Windows 2000 Server
  PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER
  Instant Activation · $99/Month · Free Setup
  http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to