>If I put a file on my apache web server and then put a link to that file on >a web page, then somebody clicks on the link and downloads the file, is it >over ftp or http? I could have sworn it's over http, but can't find the rfc >that defines file transfer over http. I've looked at rfc 1945 and 2068, but >I can't see where they talk about file transfers (though they are LONG >documents and I might have missed it). Think about it for a moment and you'll end up answering your own question. Time is up. HTTP is your answer. It cannot switch to ftp unless specifically told to do so in the link. Going to ftp would require that the ftp daemon is also running and set up to see the same physcial file locations. HTTP transfers binary data all the time, i.e., images. The Apache server will look at the extension of the file being requested to try and determine its type. When it does, it will set the appropriate MIME type in the HTTP header that is returned. If it can't match the extension, I believe it goes out as text, meaning that binary garbage will appear in the browser display area. If you don't have a standard extension for the data file, place directions on the web page telling the user to do a Save As for the following link. That way the file type is ignored and whatever the link points to is saved as a file. BTW, all HTTP transfers are file transfers. The file type that is returned tells the browser what to do with it. >Anybody know which it is, and have a reference to back it up? No reference available, just logic. >Ben MB -- e-mail: vidiot@xxxxxxxxxx /~\ The ASCII \ / Ribbon Campaign [So it's true, scythe matters. Willow 5/12/03] X Against Visit - URL: http://vidiot.com/ / \ HTML Email -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list