httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Slater <m...@analogsoftware.com>
Subject Re: [users@httpd] Read errors for GET <file> when <file> is more than 64K
Date Sun, 29 May 2005 04:12:06 GMT
After doing some more searching, this seems to be a known issue with  
Apache and MacOS X Tiger (the OS I'm running on).

See this bug --
http://issues.apache.org/bugzilla/show_bug.cgi?id=34332

See this thread --
http://mail-archives.apache.org/mod_mbox/httpd-users/200505.mbox/% 
3ce5363e1b6145ac49ad99d53c75e9fc96@stocksy.co.uk%3e

See this blog --
http://golem.ph.utexas.edu/~distler/blog/archives/000568.html

See this patch --
http://golem.ph.utexas.edu/~distler/blog/files/sendrecv.c.patch

Thanks again!

Mark

On May 28, 2005, at 8:41 PM, Mark Slater wrote:

> It has been true for every person who has visited the site,  
> regardless of browser. I even tried lynx on a unix machine within  
> the same network.
>
> I don't think it's a problem with the HTML because, first it worked  
> just after Apache was installed, and second, it worked on the last  
> version of apache I had the site running on (though it was a  
> different computer). In addition, I can view the web pages locally  
> (using a file:/// URL) and they have no problem.
>
> Mark
>
> On May 28, 2005, at 12:13 PM, Vizion wrote:
>
>
>> On Saturday 28 May 2005 11:55,  the author Mark Slater contributed  
>> to the
>> dialogue on [users@httpd] Read errors for GET <file> when <file>  
>> is more than
>> 64K:
>>
>>
>>> I compiled a clean version of Apache2 2.0.54 last week and things
>>> seemed to work fine for a few days. However, now whenever anyone
>>> tries to access a file larger than 64 K, the browser will fail to
>>> download. The failure occurs on Safari and Firefox. The access log
>>> shows a successful response, with the correct file size, but the  
>>> file
>>> is always cut off before transfer completes.
>>>
>>>
>> Is this Always true for every firefox/safari connection no matter  
>> where it is
>> from or just true for a specific test time/situation?
>>
>>>
>>> What is the best way to debug this problem?
>>>
>>>
>> Start with the above -- make sure you know whether it always  
>> happens with
>> those specific browsers. Get a number of different people to check  
>> it out.
>>
>> I think the answer is in the coding - depends upon how strict/ 
>> lapse the
>> browser..
>> The image
>> Empire_State_1.jpg
>> File size  2784522
>>   Original date  11/30/02 12:00 AM
>>   Resolution  1712 x 2288
>>   Flash  16
>>   Focal length  9.9mm
>>   Exposure time  1/500s
>>   Aperture  4.0
>>   Focus Distance
>>   Metering Mode  Evaluative
>>   Camera make  OLYMPUS OPTICAL CO.,LTD
>>   Camera model  C750UZ
>>
>> Here is an example from source code (state_1 is virtually the same)!:
>> A HREF="../Empire_State_3.JPG">
>>         <IMG SRC="Empire_State_3.JPG" WIDTH="448" HEIGHT="600"  
>> BORDER=0
>> ALT="Original image">
>>
>>     </A>
>> David
>>
>>
>> -- 
>> 40 yrs navigating and computing in blue waters.
>> English Owner & Captain of British Registered 60' bluewater Ketch  
>> S/V Taurus.
>>  Currently in San Diego, CA. Sailing May bound for Europe via  
>> Panama Canal.
>>
>>
>
>


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message