That's right: if i call pages trough CFHTTP, the weirdest things happens: for example:
there is a function that generates a html table with meters and values, if i call that page trough CFHTTP, the table will be generated but not the data in it.
Another example you can try yourself: with <cfhttp method="get"
url="" resolveurl="yes"></cfhttp>
<cfoutput>#CFHTTP.FileContent#</cfoutput> , you can call the loginpage right? Well, if you login, everything seems normal, until you want to see some data, it isn't generated properly: again: tables, pulldownmenus are generated, the data that has to be in it, not. It seems to be something with calling these pages directly.
If i include the application.dll in the url in the CFHTTP-tag nothing will show up.
Since I'm not a programmer I wouldn't know if I can get to the source code, and with it does exactly. The developers also stay very foggy on that.
Willy
>> I called it an Isapi.dll because this software developer
>> called it so(it's written in Delphi). So it isn't like he
>> said, now i understand.
>> The dll is called from the browser, that's a fact, in
>> Dcomcnfg.exe you define access rights to this software so
>> internet users can use it.That's all i know. And it runs via
>> IIS5 on a win2k server. And there is nowhere a place in IIS
>> where the dll is configured as a filter.
>
>No, you're right, it is an ISAPI application; it's just not a filter.
>
>> I've allready tried to call it with <cfhttp method="get"
>> url="" but
>> like i said before, the dll isn't working properly anymore.
>
>Are you saying that the DLL doesn't work when invoked from a browser either?
>
>> I allready suggested to the developer to work with web
>> services, but they never heard about it before, so about
>> building serious web-apps i don't have to discuss with them:
>> they have their own vision :-(. To make my own interface and
>> build another application beside the existing one would be
>> like re-inventing the wheel, isn't it?
>
>Yes, it would be like reinventing the wheel, but sometimes that's the best
>option. In the long run, it would probably be better than using CFHTTP to
>invoke an ISAPI DLL. Do you have the source code for the DLL? Do you know
>what it does?
>
>Dave Watts, CTO, Fig Leaf Software
>http://www.figleaf.com/
>voice: (202) 797-5496
>fax: (202) 797-5444
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
