DO NOT REPLY [Bug 10598] New: - Apache will break down files bigger than 64KB

[bu...@apache.org]

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=10598>.
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=10598

Apache will break down files bigger than 64KB

           Summary: Apache will break down files bigger than 64KB
           Product: Apache httpd-2.0
           Version: 2.0.39
          Platform: PC
               URL: http://213.46.22.12:8002
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_cache
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: b.scholtz@chello.nl


Check http://213.46.22.12:8002 (my new web site in development, running at 
Apache 2.0.39, this url/port will be down if this issue is fixed). Click at the 
link "Site Map" at the left navigation bar. This HTML file is 129KB big. You 
will receive only the first 64KB part of this HTML file. This also occurs with 
some other pages (for example Files - Videokaarten - NVdia, which is 64.9KB 
big) and some images which are bigger than 64KB.

You can use http://213.46.22.12:8001 to compare with (this is the production 
web site, running by IIS5 of which I want to get rid of..).

I have tried it at three different computers: an IBM PC Server 520 (NT4 
Server), a simple Celeron900 server (Win2K Advanced Server), and my BP6 Dual500 
workstation (Win2K Pro, WinMe and Win98SE). I have also tried Apache 1.3.26, 
but this didn't solve the problem. I have tried to disable the firewall, also 
without success.

The most weird is that when the pages are loaded at the servers itself (I mean, 
http://localhost:8002) then the files bigger than 64KB will be displayed 
correctly! I really cannot find a solution, I was thinking about kinda caching 
problem, but I can't find the source. However I think that it's just a problem 
on my own side, which should be easy to solve, because I have never seen this 
major problem before, even not in this Bug Database..

The httpd.conf file can be downloaded here: http://213.46.22.12:8002/httpd.conf

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org