Date: Wed, 12 Sep 2007 22:16:00 +0200 From: "Zbigniew Szalbot" <zszalbot@gmail.com> To: Mel <fbsd.questions@rachie.is-a-geek.net> Cc: freebsd-questions@freebsd.org Subject: Re: php5-5.2.3_1 / website behaves as if not enabled in httpd.conf Message-ID: <94136a2c0709121316t54f8e1fag3c3beb2381949a6e@mail.gmail.com> In-Reply-To: <200709122130.16659.fbsd.questions@rachie.is-a-geek.net> References: <20070912120014.1B87016A4C6@hub.freebsd.org> <Pine.BSF.3.96.1070913015817.13849A-100000@gaia.nimnet.asn.au> <94136a2c0709121151m209ef65ale509038ec1278c30@mail.gmail.com> <200709122130.16659.fbsd.questions@rachie.is-a-geek.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, 2007/9/12, Mel <fbsd.questions@rachie.is-a-geek.net>: > On Wednesday 12 September 2007 20:51:52 Zbigniew Szalbot wrote: > > > There's only one problem left to be solved - files with php extensions > > are not really shown in browser until I click RELOAD. Files with html > > extensions are shown without the need to reload. Thanks for your > > patience! Actually, maybe my description should be corrected - that is when I want to access a directory where index.php resides, apache will just display this directory content. But when I click (not reload) the php file, page is loaded correctly. > > To try and come to the cause, take Indexes outof Options for a given > directory/location. It should give a Forbidden at that time, reason will be > in error log, the exact request should be in access log. Look for subtle > differences if there are any - between the forbidden and the reloaded page > (like ending slash or what not). I did it for one directory where it was defined and I did get 403 error. So reading httpd-error.log: Directory index forbidden by rule: /usr/local/www/data/test/ access-log: "GET / HTTP/1.1" 403 302 Maybe I will have to say reconcile with php 4.4.7 after all. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94136a2c0709121316t54f8e1fag3c3beb2381949a6e>