kind of ot

  • Thread starter Thread starter chris leeds
  • Start date Start date
C

chris leeds

does anyone know if having fp extensions on a web/ subweb would cause
permission problems with the cgi temp file i.e. for uploads?

TIA
 
The subweb need to have folder permissions set by the host to allow files to
be uploads, and to be written to by the CGI script.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
seems that the cgi module is trying to use the root folder for a tmp file
during the upload. I've got the permissions set for the folders properly it
just seems that it's also working outside the subweb. Server admin says
it's a fp extensions conflict where in he'd have to make the root folder for
the domain writable and then anyone could edit it with FrontPage live or
whatever, that didn't sound like too good of an idea.

I'll see if they can change something in the cgi.pm for me.

remember when you told me to look for something that wasn't a pearl/ cgi
thingy...good instincts! ;-)

cl
 
The permissions need to be modified on the folder being used to allow the
uploads, and it can't be the root, so in this case the cgi.pm file will need
to be modified.

Otherwise you will need to switch to using a ASP upload component, but the
permissions also have to be adjusted on the server for the folder as well.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
see, that's the problem. the permissions are set right on the folders in
question but it seems that the cgi module is trying to use the root for the
temp file before it hits the folder it's supposed to go to.
 
Ok, then you need to open the cgi.pm file in notepad and look where it is
pointing for the temp folder, and change it to point to a temp folder within
the current folder/subweb.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
this is something unavailable to me (I think).
the server admin alluded to doing this. I'm wondering if it's something
that will be an issue for all cgi scripts running on the server.
Hopefully they'll be able to fix it. I've devised a sloppy way to get
around it but I'll have to put up a domain or subdomain without fp
extensions. I hope I don't have to ;-)

thanks for the tips Thomas!

cl
 
Chris
Are you sure it's cgi.pm at fault?
cgi.pm is a standard CPAN module that provides easy scripting for form
handlers etc., but I do not think it actually specifies where uploads are
loaded, or locations for temp files - that is usually done by the specific
form handler.
The script I use for file uploads specifies exactly where the file goes, and
does not use a temp file.
Ron
 
the developer of the script and the server admin seem to believe it's a PM
deal so who am I to argue? ;-)

it's really a cool script. I hope I get it working.
btw. server admin says it's a conflict with the fp extensions.
 
I just checked my own cgi.pm (should have done that earlier). There is
indeed a whole section of code that defines a temporary path/filename for
multipart data uploaded by a form, the default location for the temp file
being C:\temp or C:\usr\temp (on Windows machines). Since cgi.pm is
potentially used by every web on the server, the defaults are not easy to
change.

Ron

Reply only to group - all emails will be deleted unread.
 
that seems to be the problem indeed!

Ronx said:
I just checked my own cgi.pm (should have done that earlier). There is
indeed a whole section of code that defines a temporary path/filename for
multipart data uploaded by a form, the default location for the temp file
being C:\temp or C:\usr\temp (on Windows machines). Since cgi.pm is
potentially used by every web on the server, the defaults are not easy to
change.

Ron

Reply only to group - all emails will be deleted unread.


live
Click to expand...
 
Wow! the server admins fixed the issue. I haven't gotten the blow by blow
on exactly what they did but I'll let everyone know when I find out.
this is really a sign of good host/ admins. they didn't have to screw
around with my problem for a couple of days but they did.
Let this be a ray of hope for all you guys out there with bad hosting/
server admins. There are some good ones out there!
 
FYI
A cgi-bin, if you have one in a FP web, should always be converted to a subweb, and then never reopened in FP
- allows for you to open it in FTP (recommended over FP for script upload)
- allows for you to change file permissions in it
- allows for dynamic content to be created in it

IMHO
If your host is good, that folder should never be in any web for security reasons
(should be above your root web)
--



| Wow! the server admins fixed the issue. I haven't gotten the blow by blow
| on exactly what they did but I'll let everyone know when I find out.
| this is really a sign of good host/ admins. they didn't have to screw
| around with my problem for a couple of days but they did.
| Let this be a ray of hope for all you guys out there with bad hosting/
| server admins. There are some good ones out there!
|
|
| | > does anyone know if having fp extensions on a web/ subweb would cause
| > permission problems with the cgi temp file i.e. for uploads?
| >
| > TIA
| >
| >
|
|
 
Back
Top