DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16008>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16008

Damaged CGI output with larger (html) code than 64kb





------- Additional Comments From [EMAIL PROTECTED]  2003-01-12 23:26 -------
This problem probably is specific to XP but that is not quite right.
Under Win98 I'v install pure Apache2. Visual effect however was not as it 
under XP, moreover work very "quite". I mean that it works quite smooth than 
XP. But time to time IE 4 get lost for 1-2 sec.. and when I saw Access log I 
saw 4-5 queries in same seconds, i.e. IE 4 make couple of queies before result 
page to be satify (no images requested and other files requested.. only html 
page).
Also I've got and distribution: Perl+Apache+OpenSSL where the problem 
is "perfect" visable. I've tried the same scripts under HTTPS..and the look 
was terrable.. (try it).
How I've wrote.. browser find that something with page is not ok and makes 
query again and again till output page is ok.
At access.log I found a group of queries like these:

192.168.10.46 - - [13/Jan/2003:00:40:06 +0200] "GET /cgi-bin/example.pl 
HTTP/1.1" 200 85974
192.168.10.46 - - [13/Jan/2003:00:40:06 +0200] "GET /cgi-bin/example.pl 
HTTP/1.1" 200 85974
192.168.10.46 - - [13/Jan/2003:00:40:06 +0200] "GET /cgi-bin/example.pl 
HTTP/1.1" 200 85974
192.168.10.46 - - [13/Jan/2003:00:40:06 +0200] "GET /cgi-bin/example.pl 
HTTP/1.1" 200 85974

Which has the same time and file size!

I found that Apache 2 + SSL this problem is more expressive (maybe because 
Apache get slowdowned with encryption? and that takes affect to output, or 
cryped data are more sensive to errors? something like CRC?)

Anyway.. I haven't any non-standard filters ot services.. (note that problem 
is specific only to Apache 2x). Under Apache 1.3.27 everthings fine! (with and 
without SSL). Probably I've test everything I could! Even I've tried to 
shutdown one by one all started services that I think that they may be related 
to this bug.
My test "area" properties:
->Windows XP (Build 2600) Professional (without SP1)
->IE 6.0.2600
->Apache
 Server version: Apache/2.0.43
 Server built:   Dec 25 2002 18:12:51
 Server's Module Magic Number: 20020903:0
 Architecture:   32-bit
->PERL
 ActivePerl Build 804
 Built under MSWin32
 Compiled at Dec 23 2002 22:46:33

I suggest to procedure by follow way:
start example.pl and through 2sec..pres CTRL+R.. 10-15 times..and after that 
analyse Access.log file and try to find couple queries in the same second.
If no success try this with second example (with .tar.gz always I get this 
problem.. IE ask to "save as".. and when I click "Save".. it automaticaly 
close windows..and download get lost).

If this not help, probably you will need XP. Anyway I will search these days 
to find other systems with XP and I will try this again.

Note: I've lost some time to find the lower boundery, when Apache 2.x start 
produce garbage output with(without) SSL support (mod_ssl and OpenSSL - latest 
versions). The actual minimal size of produced document should be about 40kb
(50kb). So 95% of cases in that size Apache handle output correctly, but in 5% 
it force browser(IE) to refresh page, and next time almost in 95% Apache is 
able to send correct output. With 60kb(100kb) in 99.99% Apache produce damaged 
output.

Before couple of months I've got the same problem (with prvious instalation of 
Windows XP and Perl 5.6) and that's why I've deleted Apache 2 and I've back to 
1.3 for my test purposes). Moreover in one PC magazine I've read one article 
for Perl and Apache, so I've read that the author think that Apache 2 is not 
stable at this time and then I wrote a mail and ask him why (because I've got 
this problem already) and he told me that CGI output is incorect at some 
cases... so yesterday I've downloaded 1.0.43 and I was very unpleasant to find 
that Apache 2 still got the same problem, so I've decide to write  bug report).

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to