NetTalk Proxy server not working

questions
1

I am trying to make my application work with Microsoft’s DevProxy (during development) to better work with API development using NetTalk WebClient - I can get the proxy working in the Demo application with 127.0.0.1 as ProxyServer and 8000 as ProxyPort, also setting SSLCertificateOptions.DontVerifyRemoteCertificateCommonName and SSLCertificateOptions.DontVerifyRemoteCertificateWithCARoot to true - but inside the Demo application it does send and receive the request - but in my own application, it just straight goes from GET to PageReceived with no error and no data - doesn’t even make the call at all.

Now the only difference I can still find is my application is Legacy and the Demo is ABC - this can’t be it, can it? The reason it works in one and not the other?

2

Legacy or ABC wont matter. Im guessing your program just usnt set the same as the demo. Probably the Can Use Proxy switch.

But im curious as to what the DevProxy offers that you dont already have? Perhaps you ate struggling to see what actualy goes up and down the wire?

And, which build of nettalk are you on?

3

I am on NetTalk 14.30 - both Demo and my application are compiled with the same version - also CanUseProxy is set - I also tested it with setting the proxy in Internet Options - my application just fails to send anything, like it doesn’t connect to the proxy - I also checked the code inside Demo and my own, as far as I can see it should be the same.

The reason I want to use the proxy is to see what’s on the wire during development, but also be able to mock responses to test specific cases and specific logic for certain api’s.

I am glad that you confirmed it’s not a Legacy vs ABC thing, but it was the only difference I could find - I will for sure just export the TestWebClient procedure from the demo and see if I can get it running in my app - if it still fails then, then I am at a loss

4

@Bruce - thanks for the headsup - I just manually ported the TestWebClient to my application (As it’s ABC and my application is Legacy) - and it just works, so it’s a code difference somewhere - I will go check if I miss anything anywhere

5

Found my issue - I made the assumption I only get a single PageReceived so I was closing the window after, but when using the Proxy, I first get an empty PageReceived and then another with the body…

Now checking with SELF.Busy if it’s still busy

1 Like