Problems in 2.0 using ZServer ws. using IIS
I have a project that is being developed for in house use. It will need to run under IIS in order to use SSL. We are about 2-3 weeks away from deployment. I have a problem with truncated results being sent back whenever I am routing through the pcgi wrapper under IIS. Icons do not render completely (if at all) and html pages are often truncated. I access zope with http://IP-ADDRESS/scripts/zope.cgi/... When accessing via http://IP-ADDRESS:8080/... I do not encounter these problems. An article on the Microsoft Web site claims that these types of CGI problems are caused by improperly written CGI processes runnig under IIS 4.0, which implements the CGI standards more strictly than previous versions. Additionally I seemed to be able to add a new dtml method when accessing Zope via IIS 4.0. Comments? Suggestions? Observations? __________________________________________________________________ Jim Sanford ^ Database Engineer ^ ^ ^ Accelerated Technology, Inc. ^ ^ 720 Oak Circle Drive East ^ ^ ^ Mobile, AL 36609 ^ ^ ^ Voice: 334-661-5770 fax: 334-661-5788 ^ ^ E-Mail: Jsanford@atinucleus.com Web: http://www.atinucleus.com Source Code, No Royalties, Any CPU...It just make sense ! __________________________________________________________________
Jim Sanford wrote:
I have a project that is being developed for in house use. It will need to run under IIS in order to use SSL. We are about 2-3 weeks away from deployment.
I have a problem with truncated results being sent back whenever I am routing through the pcgi wrapper under IIS. Icons do not render completely (if at all) and html pages are often truncated.
I access zope with http://IP-ADDRESS/scripts/zope.cgi/...
When accessing via http://IP-ADDRESS:8080/... I do not encounter these problems.
An article on the Microsoft Web site claims that these types of CGI problems are caused by improperly written CGI processes runnig under IIS 4.0, which implements the CGI standards more strictly than previous versions.
Additionally I seemed to be able to add a new dtml method when accessing Zope via IIS 4.0.
Comments? Suggestions? Observations?
I've had (possibly similar) truncation problems, but only with MS Proxy Server 2.0 and IE. My problem was in essence MS Proxy which changed all \n --> \r\n but kept the Content-lenght: header unchanged. This made IE read only Content-lenght bytes and drop the rest, so my important JavaScript at the end got truncated by exactly the number of lines bytes ;( Netscape browser ignored the content-length and read all the file anyhow. You can check it out using telnet from a linux box by doing telnet IP-ADDRESS 80 | tee output.80 GET /scripts/zope.cgi/... HTTP/1.0 telnet IP-ADDRESS 8080 | tee output.8080 GET /scripts/zope.cgi/... HTTP/1.0 and comparing the output files. Or using a small python script that does the same. You will need two newlines after the GET.. line --------------- Hannu
At 20:27 6-9-99 , Jim Sanford wrote:
I have a project that is being developed for in house use. It will need to run under IIS in order to use SSL. We are about 2-3 weeks away from deployment.
Maybe you should switch to Apache with SSL? -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | T: +31 35 7502100 F: +31 35 7502111 | mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ---------------------------------------------
Jim Sanford wrote:
I have a project that is being developed for in house use. It will need to run under IIS in order to use SSL. We are about 2-3 weeks away from deployment.
I have a problem with truncated results being sent back whenever I am routing through the pcgi wrapper under IIS. Icons do not render completely (if at all) and html pages are often truncated.
Jim, I don't have any experience running under IIS, but Amos Lattier does. He was the first to get pcgi-wrapper.exe working with it. The Win32 hack of pcgi-wrapper was mainly a proof-of-concept thing. I tested it using Apache. Win32 incurs a substantially higher process launch cost (Unix's fork has a more efficient copy-on-write mechanism). Hopefully, Amos will join this thread. Until then, one suggestion might be to set the System Environment Variable: PYTHONUNBUFFERED=1 (or set in Zope.cgi). Good luck. Jeff Bauer Rubicon Research
At 01:27 PM 9/6/99 -0500, you wrote:
I have a project that is being developed for in house use. It will need to run under IIS in order to use SSL. We are about 2-3 weeks away from deployment.
I have a problem with truncated results being sent back whenever I am routing through the pcgi wrapper under IIS. Icons do not render completely (if at all) and html pages are often truncated.
I haven't run PCGI with IIS for a while, but I recall problems like these a long time ago. IIRC, there was an issue of IIS replacing all newlines in returned output with CRNL, even binary responses. This breaks images and causes problems with content-length headers no longer being valid. Argh! There may be some IIS knob to adjust this, but I don't know what it is. As for the truncation, I'm not sure. I haven't seen this.
I access zope with http://IP-ADDRESS/scripts/zope.cgi/...
When accessing via http://IP-ADDRESS:8080/... I do not encounter these problems.
An article on the Microsoft Web site claims that these types of CGI problems are caused by improperly written CGI processes runnig under IIS 4.0, which implements the CGI standards more strictly than previous versions.
Hmm. Any specifics on what has changed? I'd be more than happy to help with fixes to these problems if I had a little more to go on in terms of what IIS is expecting that it isn't getting. Sorry that I can't be of more help. -Amos
participants (5)
-
Amos Latteier -
Hannu Krosing -
Jeff Bauer -
Jim Sanford -
Martijn Pieters