.html problems
we can transfer files to a freebsd server from XP. Everythime we try to upload index.html it goes from 850kb to 828kb and it always displays the same text index directory??? is that o the XP side or free bsd side... I see the new file on the BSD server, but the same crappy index of/ page keeps coming up... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: .html problems
On Monday 31 January 2005 18:50, kip winston wrote: we can transfer files to a freebsd server from XP. Everythime we try to upload index.html it goes from 850kb to 828kb and it always displays the same text index directory??? is that o the XP side or free bsd side... I see the new file on the BSD server, but the same crappy index of/ page keeps coming up... I'm not quite sure what you are asking here but anyway... I found that uploading in ASCII mode can change the line endings from DOS to UNIX and similar. This may be where your missing bytes are coming from. As for 'index of /' page, sometimes it will only accept index.htm not index.html. This can be changed in the config file for Apache though. Hope I'm answering the right question. -- /Xian Whoever undertakes to set himself up as a judge of Truth and Knowledge is shipwrecked by the laughter of the gods. Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: .html problems
we can transfer files to a freebsd server from XP. Everythime we try to upload index.html it goes from 850kb to 828kb and it always displays the same text index directory??? is that o the XP side or free bsd side... They probably treat trailing whitespace on lines differently. That could account for some difference. Also, if you used ftp to transfer the file in ASCII mode, then it would have chopped off a CR character from each line because UNIX uses just LF to terminate a line whereas MessyDOS uses CR-LF to terminate a line. Try looking at the file with a text editor such as vi. First of all, did it get put in the correct directory for your configuration? If it looks like html, eg starts with html and ends with /html or other recognizable stuff, then it probably got transferred OK. The next thing to check is is the ownership and permissions are OK. The file should be readable by the web server (Apache probably) Finally, you should look at the name of the file and what is configured in the web server (httpd.conf).Mostly, Apache's httpd.conf starts out configured to recognize .html names files, but not .htm or other variations including .HTML or .HTM which you often get when moving a file from MustyDOS.Remember that UNIX is case sensitive. If the case or .html vs .htm is the problem you can either just rename the file on the FreeBSD system to a lower case only name or go in to the httpd.conf file and add those variations to it. I think I remember it is the DirectoryIndex index.html index.htm index.HTML etc etc etc directive that does it. Those are the first things I would check. After that, well, I don't know. I see the new file on the BSD server, but the same crappy index of/ page keeps coming up... That will happen when it doesn't see a readable file with one of the acceptable names in the DirectoryIndex directive. You can turn off indexing and then you would see an error message instead of the directory listing. To do that remove the work Indexes from the Options directive that applies to your directory where the web page lives. Looks something like: Directory /usr/local/www/data Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny Allow from all /Directory jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: .html problems
where is the (httpd.conf) file? it is not in /etc No ports config files should go directly in to /etc. You could have a really hard to read and manage mess then. the httpd.conf file will be wherever you told the apache install to put it. A likely place would be /usr/local/etc/apache/which seems to be the current thinking on how to install ports/third party software. I think the ports install now puts it there by default. But I have machines with it in /usr/local/web/conf as well. They are from an earlier era. Note that there may be a couple of other .conf files srm.conf and access.conf in particular. Those are vestigial and all of their function has been rolled in to httpd.conf so don't put anything in them, just the httpd.conf file. jerry On Mon, 2005-01-31 at 15:45 -0500, Jerry McAllister wrote: we can transfer files to a freebsd server from XP. Everythime we try to upload index.html it goes from 850kb to 828kb and it always displays the same text index directory??? is that o the XP side or free bsd side... They probably treat trailing whitespace on lines differently. That could account for some difference. Also, if you used ftp to transfer the file in ASCII mode, then it would have chopped off a CR character from each line because UNIX uses just LF to terminate a line whereas MessyDOS uses CR-LF to terminate a line. Try looking at the file with a text editor such as vi. First of all, did it get put in the correct directory for your configuration? If it looks like html, eg starts with html and ends with /html or other recognizable stuff, then it probably got transferred OK. The next thing to check is is the ownership and permissions are OK. The file should be readable by the web server (Apache probably) Finally, you should look at the name of the file and what is configured in the web server (httpd.conf).Mostly, Apache's httpd.conf starts out configured to recognize .html names files, but not .htm or other variations including .HTML or .HTM which you often get when moving a file from MustyDOS.Remember that UNIX is case sensitive. If the case or .html vs .htm is the problem you can either just rename the file on the FreeBSD system to a lower case only name or go in to the httpd.conf file and add those variations to it. I think I remember it is the DirectoryIndex index.html index.htm index.HTML etc etc etc directive that does it. Those are the first things I would check. After that, well, I don't know. I see the new file on the BSD server, but the same crappy index of/ page keeps coming up... That will happen when it doesn't see a readable file with one of the acceptable names in the DirectoryIndex directive. You can turn off indexing and then you would see an error message instead of the directory listing. To do that remove the work Indexes from the Options directive that applies to your directory where the web page lives. Looks something like: Directory /usr/local/www/data Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny Allow from all /Directory jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
