Violinist with WebAPI acts flaky

We have an environment in which we use web api with .NET CORE, and since we cannot host it in IIS, we use a script for a proxy server. Now I have a .NET client that calls this service.

However, the service call is very unstable, it can make several callbacks, and then suddenly stops, even if nothing changes between calls. It is really "flaky." Not sure what makes him behave inconsistently.

I looked through some articles, and they suggested having ipv6.fiddlereither localhost.fiddlerlike my url, but nothing helps.

I also went and updated my configuration file, as mentioned here on the Telerik website. This also does not work.

Any ideas?

+6
source share
1 answer

In my understanding, connecting to a local host may not always work. This also happened to me. As a related article states that

Allow the .NET Framework to automatically connect to Fiddler, run Fiddler before running the .NET application, and

, localhost, localhost , ( , wirehark netmon ..), localhost. localhost URL-, U ,

  • Fiddler , -
  • ipv4.fiddler
  • - .net - .net.

- localhost. , -, .

e.g. http://localhost/api may or may not appear in fiddler but http://mymachine/api will always be captured.
+2

Source: https://habr.com/ru/post/1017303/


All Articles