[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date
][Minivend by thread
]
Re: Fw: [mv] Problem report, error 404, no access to catalog
Hello there,
that's the way I like it, thanks for your attention.
>Kyle wrote:
>404 errors:
>1. you are sure that there is a file called "simple" in your cgi-bin
>correct?
Yes, I am. - /www/cgi-bin/simple -
>2. If so are there any other files in your cgi-bin? If so, do they work?
Yes, there are other files, .cgi, .pl and executables without extension like
the simple executable.
>3. If there are no other files there, then put a file (any file will do
lets
>say it is called file.txt) in your cgi-bin. Then call it in your browser :
>http://www.homa.de/cgi-bin/file.txt
cgi's called from html-sites run (i.e. the counter) quite well, all files
run quite well while executing from the telnet connection. But nothing
operates when calling directly through the browser. Everytimes I receive the
404 error.
>You should receive a different error now, if you still receive a 404 error
>for this file, then it sounds to me like either:
>a) you have made up your own cgi-bin,
No, I didn't.
> but there is a different cgi-bin
>(or other named) directory where the server is actually looking.
>OR
>b) your isp has your ScriptAlias (terminology may differ with webserver)
>pointing to a wrong location (they would have to fix)
>ScriptAlias works like this:
>ScriptAlias /cgi-bin/ /path/to/cgi/directory/anywhere/on/server/
>so a url like www.yourdomain.com/cgi-bin/simple would actually
>be looking for the file simple here:
>/path/to/cgi/directory/anywhere/on/server/simple
>The most common settings for ScriptAlias is to point to
>a cgi-bin (or other name) directory that is either located
>in your root directory, or in your document directory (where
>your normal web pages are)
>If you still can't get anywhere, simply ask your isp where cgi
>scripts should be placed for your domain.
He told me the /www/cgi-bin directory is the correct directory!
>Hope this helps.
>Kyle Cook (KC)
Stefan wrote:
>If MiniVend successfully starts in inet mode, you could reach the catalogs
>etc. at
>http://www.homa.de:7786/simple
I tryed that and got some new errors. The file could not been executed
because of a Server or DNS-Error. I got this through the browser.
>If the port is already used, you get an error message in the error.log
>in the MV installation directory.
Indeed, in the /mvend/error.log I got _Runtime error: Need URI::URL for this
functionality_. I saw that modul beeing installed from the perl/CPAN during
the configuration of minivend and there was no error about it would have not
been installed. I reconfigured the whole installation with no success again.
Please, don't tell me I have to install it manually!? I don't know if I have
the permissions to do that on my ISP's server via telnet.
>See the docs for more information.
>Ciao
> Racke
It still doesn't work. Have you any idea which way to go on?
Holger