Home/ Questions/Q 5970735
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T20:25:02+00:00

I have a fairly strange(IMO) issue here with a webservice provided by a third

  • 0

I have a fairly strange(IMO) issue here with a webservice provided by a third party.

On calling the webservice on the live server, all works as expected. Calling it on a development setup, sometimes returns with a 503 - Service unavailable, other times it works. Intermittent….
Both of these tests are done from the same client, so I don’t think its a network level problem.

Now, the strange thing is, if I place a breakpoint on the line before the webservice call, and step over the call, it works. Even running the code(F5) past this breakpoint allows it to succeed. Adding a System.Threading.Thread.Sleep(1000); before the call(to simulate a breakpoint, of sorts), doesnt have any effect.

I don’t have access to the remote servers, I know its server 2003/IIS 6.0 though, and the company that provides the system the webservice interfaces with, claim there’s no issue with their server / software.

So before I go seriously pointing the finger, anyone experienced anything like this before, or anything else I can try?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In the end, this was caused by a issue on a transparent(ip spoofing) proxy, that sits upstream between my system and the remote system. The proxy was returning the 503, but under the guise of the target host.

    I only managed to find this by fluke, how would I have identified this if I was to look for this type of issue, as theres nothing in the http headers /raw dump that jump out at me to point to this issue?

    • 0