comp.os.linux.networking

I ran into this issue also and found the resolution. Here's the
information I found - http://nixforums.org/about127225.html

Just set the following in your httpd.conf file -

EnableSendfile off


On Mar 12, 6:24 am, Rick Onanian wrote:
> On Mar 11, 1:35 pm, Jack Snodgrass
> wrote:
>
> > what does the apache error log show ( if anything ).
> > What does the apache log file show for the filename.jpg file?
> > If you get a good return code in the apache log... does the bytes
> > sent match the file size?
>
> Nothing. I was thinking maybe I should turn up the logging level.
>
> > Does it work with smaller files and just not larger files.
>
> No, I tried with very small files (~300 bytes), small files (50k), and
> somewhat larger files (2mb).
>
> > Can you do cp filename.jpg /tmp and have it get copied correctly?
>
> Yes.
>
> > what does wget -O erase.me "http://127.0.0.1/directory/filename.jpg"
> > give you when you run it from your webserver. does the erase.me
> > file have the correct number of bytes when the transfer completes?
>
> Good idea, I hadn't thought of that. The output is interesting,
> actually:
> -=-
> [root@student tmp]# wget 'http://127.0.0.1/~collegepictures/2006/
> SmartBoard/SmartBoard.jpg'
> --09:18:00-- http://127.0.0.1/~collegepictures/2006/SmartBoard/SmartBoard.jpg
> => `SmartBoard.jpg'
> Connecting to 127.0.0.1:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 763,685 (746K) [image/jpeg]
>
> 0%
> [ ]
> 0 --.--K/s
>
> 09:18:00 (0.00 B/s) - Connection closed at byte 0. Retrying.
>
> --09:18:01-- http://127.0.0.1/~collegepictures/2006/SmartBoard/SmartBoard.jpg
> (try: 2) => `SmartBoard.jpg'
> Connecting to 127.0.0.1:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 763,685 (746K) [image/jpeg]
> SmartBoard.jpg has sprung into existence.
> Retrying.
>
> --09:18:03-- http://127.0.0.1/~collegepictures/2006/SmartBoard/SmartBoard.jpg
> (try: 3) => `SmartBoard.jpg.1'
> Connecting to 127.0.0.1:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 763,685 (746K) [image/jpeg]
>
> 0%
> [ ]
> 0 --.--K/s
>
> 09:18:03 (0.00 B/s) - Connection closed at byte 0. Retrying.
>
> --09:18:06-- http://127.0.0.1/~collegepictures/2006/SmartBoard/SmartBoard.jpg
> (try: 4) => `SmartBoard.jpg.1'
> Connecting to 127.0.0.1:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 763,685 (746K) [image/jpeg]
> SmartBoard.jpg.1 has sprung into existence.
> Retrying.
> -=-
>
> I like that "sprung into existence" thing. :) Anyway, at that point I
> gave up and hit ctrl-C.
>
> Okay, I googled for that sprung into existence bit and found this,
> which makes sense:
> http://www.mail-archive.com/w...@sunsite.dk/msg07365.html
> I didn't even notice but it was incrementing the filename before
> saying it sprung into existence.
>
> > Just wondering if the web server is having access files for 'large'
> > files or files after 'x' bytes and your just not seeing it getting
> > a directory index listing.
>
> It's definitely not an issue of file size.