Upload script problems

Anon

I've set up upload script on my win2k server but there is problem with uploading files.
Readme says that directory has to have 777 permissions, but of course I can't CHMOD that direcory.
What have I to do?

alcapone

nothing, just make sure your directory is writable

cheers,
AlCapone

dzekic

It is, but for owner...
I mean it's attributs are "drwxr-xr-x". How could I set it to be writable?

Anon

The attributes should read drwxrwxrwt ...

On linux simply type chmod 1777 dir_name where dir_name is (obviously) the name of the dir you wish to upload to.

On win2k, I don't know... maybe right click on dir, select properties and make sure it's NOT set "read only".

Anon

I've run into this issue myself. I use WinMe. My web host says, for any files I upload (FTP, whatever) that I cannot write or append to them. Apache owns these files, not me! I can delete them, or download them of course, but that is all I can do.

The only other option I have is allowing my script to create the file on their server. Then, because they allowed me ownership of the folder this file is in, I can append or write to the file -- that is all I can do.

This is too restricting, as my website depends upon my customers writing to files I create (which I may wish to edit from time to time). So I'm looking for a web host that will give me complete and total control over my files. Apache be damned.

Anon

I use a PHP application call Owl Intranet Knowledgebase and had similar upload issues when running Apache 1.3.20, PHP v4.0.6 under WinNT and Win2K.

The way I got round uploading is that the browser settings need to change. Goto the Tools->Internet Options->Advanced. Find the HTTP 1.1 Settings and uncheck everything.

If you are authenticated using HTTP 1.1, you will need to logoff, close the browser and restart the browser. Try uploading again.

If it works for you, do let me (us) know.

BRegards,
James

Anon

Apache is the No.1 web server world wide...
if it is configured properly then apache does NOT own the files that sit on the server.

The owner will be YOU, ie the person who has uploaded the file to the server, the person who has WRITE permissions to the directory known as Apache's DocumentRoot.

Apache runs with the same permissions as every one else in the world, ie it has no power to write to files that are stored on the document tree, and this is how it should be... after all, we don't want just anyone writing to our precious files, do we.

If you want to write to files that are already on the server, you don't use apache to do it, you use php or perl or some other tool like that. And of course you first have to set the permissions on your file to allow that process.

If you are in fact unfortunate enough to be hosted on a server that is not properly configured, then definitely look for another host... but make sure you know what the problem is first.

Anon

According to my web host, any files I FTP to their server are owned by me. And files I create via a PHP script are owned by Apache. They gave me write permissions for these types of files.

You may be right, things are not configured correctly. I never had this problem with Verizon. And if they weren't charging an arm & leg for their services, I would still be hosting with them.

Thanks for your input.

Anon

Correct... if you use php to write the file it is owned by apache. This means apache/php will be able to write to or remove the file whereas it will deny you permission to do the same if you log in via telnet or ftp.

If you want to let php or perl write to files you upload via ftp, you need to set the file permissions to allow anyone, that is the world, aka other, to write to your file.

You can do this in WS-ftp by right-click the file on the remote server, select chmod(UNIX), then set write for user, group and other.