I am using IIS 6, FoxWeb 3.3, and ASP.NET 2.0.50727. ASP.NET is the new web development model for my organization; however we have a large library of FoxWeb scripts that we would like to continue using rather than rewriting them.
The FoxWeb scripts perform black-box functions such as FoxPro database queries/updates, interface to third-party authentication systems, manage security lists, send e-mail notifications to distribution lists, etc. Calling these FoxWeb scripts from a web browser such as IE6, IE7, FireFox 1.5, or HTTP socket libraries from inside a FoxPro application all work fine. Everything works as expected with ASP.NET 1.1 web pages as well. It wasn't until ASP.NET 2.0 that the problems started occuring.
The code in the ASP.NET 2.0 pages that is breaking looks something like this:
req = HttpWebRequest.Create("http://dev.server/foxweb.fwx?form_id=notify&appcode=register")
resp = req.GetResponse()Some people have suggested that I modify the web.config file for ASP.NET but this doesn't seem to work.
<system.net>
<settings>
<httpWebRequest useUnsafeHeaderParsing="true"/>
</settings>
</system.net>I realize this might be a bug in ASP.NET or a server misconfiguration that is unrelated to FoxWeb, but I'm curious if FoxWeb is indeed sending a CRLF after each of the response headers that it sends.
-Brent