Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WebService Wrapper
Message
From
09/10/2001 10:22:19
 
 
To
08/10/2001 22:19:29
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
00565223
Message ID:
00565919
Views:
14
>Setting oClient.ClientProperty("ServerHTTPRequest") = .T. did the trick.
>
>I didn't set any registry entries to make it work. Just setting "ServerHTTPRequest" to .t. worked for me.

Hmm. What version of the toolkit are you using? I've tried this before and it _didnt_ work for me.

>If I call someone else's WebService from within my WebService by setting "ServerHTTPRequest" to .t. is that a security risk?
>You mentioned that doing this was not safe can you elaborate a little on this please?

It's not a security risk that I can see. I was talking about WinInet.dll when I said unsafe. 'Unsafe' for server use simply means that using it in a server environment is not dependable. In the case of WinInet, it's for a couple of reasons, the Proxy config issue is one of them. Its threading model is another, but this one would only get in the way under relatively high volume.
Erik Moore
Clientelligence
Previous
Reply
Map
View

Click here to load this message in the networking platform