You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/04/20 11:36:47 UTC
DO NOT REPLY [Bug 28491] New: -
Largefiles with Partial Content and Content-Range Header
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28491>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28491
Largefiles with Partial Content and Content-Range Header
Summary: Largefiles with Partial Content and Content-Range Header
Product: Apache httpd-1.3
Version: 1.3.28
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: core
AssignedTo: bugs@httpd.apache.org
ReportedBy: whurst@whurst.net
Hi. We still have trouble with Largefiles (2GB and more) and with (206) Partial
Content (Content-Range Headers). We have analyse the Traffic. We see the Apache
Server can not write values greater than 2GB correctly. The Content-Length will
have a negative value. I fixed this in the source, but the Problems are still
alive on the Content-Range Headers. The problem is, the internal Apache Code
will work with a LONG C-Type. The LONG C-Type is ONLY 32 bit (GCC,
Solaris/SPARC). If i compile with LARGE_FILES options (man lf64) that will not
work, because the Apache does not use OFF_T C-Type. We have fixed this manually
in serverals Sourcecodes (protocol.c, core.c, ...) but something will go
strange, the Apache will core.
We have an internal system with many files greater then 2GB. Our View-Tool will
now (after a patch party) work with Partial Content greater then 2GB. But the
Apache give us negative numbers, all the time. Our view-tool will not work ....
You can contact me all times. i try to fix the problem, but i think i need help,
because, this problem is very global.
Using of GCC -m64 (64 bit compile) -> long's are 64bit, will NOT work, because
GCC is not really 64bit able, and the code will be very very slow ....
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org