The following reply was made to PR general/1380; it has been noted by GNATS.

From: Marc Slemko <[EMAIL PROTECTED]>
To: Apache bugs database <[EMAIL PROTECTED]>
Cc:  Subject: Re: general/1380: cgi script fails to load gif  (fwd)
Date: Mon, 10 Nov 1997 10:05:54 -0700 (MST)

 ---------- Forwarded message ----------
 Date: Mon, 10 Nov 1997 16:42:10 +0000
 From: Ferret <[EMAIL PROTECTED]>
 To: Marc Slemko <[EMAIL PROTECTED]>
 Cc: [EMAIL PROTECTED]
 Subject: Re: general/1380: cgi script fails to load gif 
 
 
 >On Mon, 10 Nov 1997, Ferret wrote:
 >
 >> 
 >> >Synopsis: cgi script fails to load gif
 >> >
 >> >State-Changed-From-To: analyzed-closed
 >> >State-Changed-By: marc
 >> >State-Changed-When: Mon Nov 10 07:56:11 PST 1997
 >> >State-Changed-Why:
 >> >User was not putting proper path in.
 >> 
 >> So how do I tell the cgi to display the image instead of trying to run it
 >> as a cgi script?
 >
 >Huh?  Don't put images in ScriptAliased directories.  
 
 I don't want to, but whenever I refer to a file in the cgi code it
 magically gains machine-name/cgi-bin before the path I give. Thus not
 finding the file i realy wanted. If I move the file to where it is looking
 it is then in a ScriptAliased directory and will be treated as a script,
 like I said not very useful for an image.
 
 >
 >> 
 >> Also I can't have made it clear, but I *was* giving it the full and
 >> correct path to the image but Apache changes that to be relative to the
 >> cgi-bin directory regardless of what you tell it. This is fine if you only
 >> want to run scripts but not very helpful if you want to display an image.
 >
 >Apache does not change it to be relative.  Apache has nothing to do with
 >it; it is between your CGI and your web client.  In the example you gave,
 >you were giving a relative path.  That path is relative to the CGI script.
 
 Yes we realised that and tried giving a full path. See above
 
 
 Ok we found our problem(s) - 1. some of the code had \ between directories
 not / (we move it from the linux box, yup we do feel stupid)
 
 2. We have a corrupt gif on another machine
 
 3. We had missed the / in front of the file name on the one where we had
 checked the gif. (yup we feel even more stupid on that one)
 
 Thanks for your help
 
 problem fixed
 
 
 Ferret
 
 --
 
 I'm no upstanding citizen, but I'm standing up just the same -- Poison
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ~                [EMAIL PROTECTED]   |   Micro$oft: Just say no!            ~
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

Reply via email to