Still broken. No ideas here? It seems the wc.dll never sees the .tmp file response and then serves up the timeout page. How could that happen if I can see the .tmp file get created and I can open it and confirm all the html is present? Because wc.dll is a black box, I have no idea of knowing why it's not returning the contents of the response .tmp file to the browser.
Either a windows update broke something or I inadvertently broke something but I don't recall changing anything.
In my dev environment (WC4 file based mode) my application will respond one time to a request, I can see the .tmp file get created in the temp folder, but this tmp file never gets delivered back to the browser. If I look in the temp folder wcerrors.txt I see two Web Connect Request timed out records for each request. Error # -2 and then a few milliseconds later error# 1008
Once my app serves one request it will not serve any more requests until I exit the WC monitoring form and restart myappmain.prg
Here's the kicker. If a make a build and push to a web server it runs fine.
I tried deleting the site out of IIS and resetting everything up but that doesn't work. Any ideas?
