I have a web service that takes some 15 seconds to calculate the results, then it sends a JSON back to the client.
With a delphi app, with regular javascript parsing, Ajax or any other method, the client waits and displays the results.
However when trying to implement it on EWB 2.06 R15, it seems that the  TServerRequest just ignores the timeout settings (i set it to 20000 mS)  and it fires the RequestComplete event immediately, of course it has an empty response.  I placed a debug showmessage to print the actual response inside the RequestComplete event.

If the server responds within a few milliseconds everything is normal, but with this web service it does not wait.  

Could it be a bug?

 

Try to find out what is sent to the server (on HTTP level) and what comes back
as an answer. Try firefox or crome for example, press F12, click the network tab,
re-send your request and inspect the server response.

Michael Dreher

Michael Dreher wrote:

> Try firefox or crome for example, press F12, click the network tab,
> re-send your request and inspect the server response.

WHS - the browser's network debugging will reveal all. I had a similar thing and it was all down to cacheing - the server had responded before to the same request so it said "just use previous" and the browser obeyed. Telling the server to send "no-cache" headers will probably fix.

--

Matthew Jones