Very Computer

> This works:
>  mount -t smbfs -o username=smbusername,uid=apache,ro //server/share
> mountpoint/
> but it complains that smbfs is deprecated and I should be using cifs.
> For now, I'm using it anyway.

> This seems to work:
>  mount.cifs //server/share mountpoint/ -
> ouser=smbusername,uid=apache,ro
> but it won't serve actual files. It allows browsing of the directories
> and shows the filenames. It does not return an error, it just does not
> send the file. I have confirmed that user 'apache' can read the file
> by logging in as that user and viewing the file.

> I tried a telnet test, using GET and Host commands captured from
> firefox's LiveHTTPHeaders extension, like this:
> -=-
>  telnet webserver 80
>  GET /directory/filename.jpg HTTP/1.1
>  Host: webserver
> -=-

> The result looks like this:
> -=-
>  HTTP/1.x 200 OK
>  Date: Tue, 11 Mar 2008 15:51:07 GMT
>  Server: Apache/2.2.4 (Unix) PHP/5.2.0
>  Last-Modified: Thu, 21 Feb 2008 16:07:30 GMT
>  Etag: "420f8a5-180bf4-4d7a7480"
>  Accept-Ranges: bytes
>  Content-Length: 1575924
>  Keep-Alive: timeout=5, max=100
>  Connection: Keep-Alive
>  Content-Type: image/jpeg

>  Connection to host lost.
> -=-

> > 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:
> -=-

> 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:

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