Forum Home
Press F1
Thread ID: 53459	2005-01-18 06:01:00	Mysterious 404	george12 (7)	Press F1

Post ID	Timestamp	Content	User
315388	2005-01-18 09:12:00	Cheers ninja, I think you've got it. Now I get a new error message: Security Alert! The PHP CGI cannot be accessed directly. This PHP CGI binary was compiled with force-cgi-redirect enabled. This means that a page will only be served up if the REDIRECT_STATUS CGI variable is set, e.g. via an Apache Action directive. For more information as to why this behaviour exists, see the manual page for CGI security. For more information about changing this behaviour or re-enabling this webserver, consult the installation file that came with this distribution, or visit the manual page.	george12 (7)
315389	2005-01-18 10:10:00	says this: "Read your php.ini file, the "Paths and Directories" section. It tells you that if you're using IIS you must set cgi.force_redirect = 0 " See if that does it... RW Google first, ask questions later? Google (www.google.co.nz essed+directly.&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official) Perhaps: During the install the windows PHP installer puts the php.ini file in the "C:\Documents and Settings\Administrator\WINDOWS" folder. It must be moved to (%SYSTEMROOT%\php.ini). Once I did that everything works fine.	ninja (1671)
315390	2005-01-18 11:13:00	Fixed. Thanks very much again ninja :)	george12 (7)
315391	2005-01-19 03:02:00	What is the problem. That's exactly how HTTP is supposed to work. :D There is no file "... katoons.com/forum". It's the name of a directory. URLs refer to files. The many people who try to access sites by typing in " should receive a 404 too. ;) You should either give the "/"" target="_blank">this.is.not.a proper.url.com" should receive a 404 too. ;) You should either give the " at the end, or an actual filename of the object required. You might find that "...katoons.com/forums/" (note the "/") will work. That now is trying to access the contents of the directory. If there's no default index file, most http servers will format up a directory listing in HTML and send that. There's usually a well defined default index file in the home directory of a site. I think that most servers or browsers will try to help out by adding a slash if it's missing. But a strict reading of the protocol says it's an error. You can certainly fix the configuration file for that customer. It obviously hasn't got "index.anything" being served up when the caller makes an error. Looking back I see I am talking about "forced redirection", and while I have been writing this you've been getting the answer. :D	Graham L (2)
315392	2005-01-19 04:27:00	schtuff It wasn't working because the files weren't configured to be procesed properly by the webserver. The other problem is that IIS servers in their infinite greatness spit back a 404 error for everything, rather than just page not found.	ninja (1671)
1 2