chmod Images

[Jadzia]

I have just tried linking to my "missing" images on my secure server directly and recieved the following error.

 

CGIWrap Error: Execution of this script not permitted

 

Execution of (oscommerce/x-scripts/oscommerce/images/notop1.jpg) is not permitted for the following reason:

 

Script is not executable. Issue 'chmod 755 filename'

 

Now the fix is easy - chmod the images. My question is WHY would it require images to have this permission level?

 

Thanks for any responses

 

Christina

[Guest]

...

Now the fix is easy - chmod the images.  My question is WHY would it require images to have this permission level?

<{POST_SNAPBACK}>

Not certain, but it could be the way jpg image handling is defined in your web server configuration - the need for exec permissions could be an anomaly introduced by the jpeg handler. I would investigate this area, if it were me.

 

By the way, if you are using apache, then it is much better to use the php execution module rather than the cgi interface. It is much more efficient and has some other benefits too - see the php web site for more details. If you do this, you won't have to add execution permissions to the php files either.

 

Rich.

[Jadzia]

Not certain, but it could be the way jpg image handling is defined in your web server configuration - the need for exec permissions could be an anomaly introduced by the jpeg handler. I would investigate this area, if it were me.

 

By the way, if you are using apache, then it is much better to use the php execution module rather than the cgi interface. It is much more efficient and has some other benefits too - see the php web site for more details. If you do this, you won't have to add execution permissions to the php files either.

 

Rich.

<{POST_SNAPBACK}>

 

Thanks :D chmoding didn't help and I am so brain fried from getting ssl working with a shared ssl on two servers I decided to re-install and trty again.. I am unsure of what you mean by php execution module - is that in oscommerce or phpmyadmin? I REALLY am brain fried.! :blink: :o :'(

[Guest]

... I am unsure of what you mean by php execution module...

<{POST_SNAPBACK}>

With apache, you can execute php two different ways :

 

1) Via the cgi interface

2) By building the php engine into apache itself (actually, it is often loaded as a module into apache at start up)

 

The first option is very inefficient because apache has to load and start the php engine separately for EACH page that is requested. With the second option, the php engine is pre-loaded into apache and it can re-use it as each page request is processed. This is a major advantage of php over other scripting languages such as perl (Ignoring the fact that perl seems to have been designed by throwing spaghetti at a wall and seeing where it lands :-) ) and is how php is normally used. This option is only available for apache though. See the php web site for further info.

 

Rich.