FoxWeb 2.0 automatically adds the Content-Type header, unless you override it with Response.ContentType method. Including the content type with the Response.Write method should not make a difference and in fact it will probably cause the content type command to be displayed in the browser window.
Sent by Jeff on 08/16/2002 08:41:32 AM:
I may have found the problem. I use a single .FWX to call all my request and use parameters to indicate where I want to go so it was simple to add :
response.write("Content-type: text/html" + chr(13) + chr(10) )
before sending any output to the browser. This seems to have cured the problem so far but we will test a lot over the next few days. This application normally runs on our main web server with 3.5 NT and handles about 200 part time users on a day to day basis. I'm converting from ASP to Foxweb. For testing I've been using a 1.2 MHZ running XP professional if that any help.
Sent by FoxWeb Support on 08/15/2002 10:22:23 AM:
I have never seen this problem before. Does it occur with your code only, or do you see the same problem when you run the sample applications that were installed with FoxWeb, such as ContactMine?
Sent by Jeff on 08/15/2002 08:42:53 AM:
I get the following error constantly. I can't relate it to a slow response time or large files. Any Ideas. I will insert itself at random into the the HTML code as it's sent back to the browser window using "response.write()"
Using VFP 6.0 with the one month version of 2.11.
"HTTP/1.1 200 OK Server: Microsoft-IIS/5.1 Date: Thu, 15 Aug 2002 15:38:11 GMT Connection: close "