RE: [cobalt-users] CGI Permissions

["dlyles" <dlyles@xxxxxxxxxxxxxxxxxxx>]

Thanks for everybody's help.  I didn't write the script, so I'm passing this
info to the programmer.

-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Nell Bolen
Sent: Saturday, February 23, 2002 5:49 PM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] CGI Permissions


dlyles wrote:

I am using a Raq3 as a dedicated server plan.  I have set up a
domain with CGI capabilities, but need it to have read/write
permissions.  I
though I did this correctly, my CGI (and my Cobalt) knowledge is very
minimal.  I'm currently getting an error when I run the script.  It's
easier
to just see for yourself at

http://www.ascentimentaljourney.com/homespa/homespa_ll.htm

Just check out any item and you'll see the error.  The developer of the
site is telling me
it's a permissions situation, which I thought it shouldn't be.

David wrote:

This is common with cgi.  Make sure you have the path correct as the
error
states and just for grins use the full
http://pathtoyoursite/cgi-bin/your.cgi

chmod the script 755
ssh or telnet in.
change to the directory
su to root
type chmod 755 quikstor.cgi

Where did you get the quikstor.cgi script?

dlyles wrote:

I got the script from the clients programmer.  I see your directions
type
chmod 755 quikstor.cgi.  Am I typing this as written?  Forgive my telnet
ignorance.

Hello,

1. Check each cgi script first line. For the RAQ 4i here, first script
line needs to be

#!/usr/bin/perl

#!/usr/local/bin/perl (sometimes a script default line) won't work.

2. On this server, chmod 755 scriptname.cgi functions in any directory
(RAQ default directory permission I think)

3. If your script(s) write to other file(s), those files need write
permissions (what kind of write permissions depends upon who will be
doing the writing (owner, group or world)

4. Didn't see your cgi error message, but make sure any variable
pathways in the script(s) are correct -- full virtual path works best
here, i.e.,

/home/sites/sitexx/web/script-directory-name

(no trailing slash unless script comments tell you to)

For CGI URL variables, full http pathway, including the www, works best
here:

http://www.yoursite.com/script-directory-name/script-name.cgi

5. Exceptions:

Have not yet figured out why, but sometimes in some scripts here, a
variable, set a the beginning of a script and used throughout the
script, such as:

$script_url = "http://www.yoursite.com/yourdirectory/scriptname.cgi

doesn't work later in the script calls. In those cases, if we replace
the variable $script_url with the full http pathway

(http://www.yoursite.com/yourdirectory/scriptname.cgi

Well, the script will then run correctly. Sometimes if we omit the "www"
part of the pathway, script won't work, sometimes it will. Am always
interested in the whys of stuff like this, so please explain these
exceptions, anyone who can.

Thanks, Nell Bolen
nell@xxxxxxxxxxxxxx

_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users