Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 10194 invoked by uid 500); 2 Jul 2002 11:34:07 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 10183 invoked from network); 2 Jul 2002 11:34:07 -0000 Received: from smtp1.jp.viruscheck.net (154.33.69.52) by daedalus.apache.org with SMTP; 2 Jul 2002 11:34:07 -0000 Received: from [154.33.69.36] (helo=mail2.jp.viruscheck.net) by smtp1.jp.viruscheck.net with esmtp (Exim 3.16 #2) id 17PLuG-000GBf-00 for users@httpd.apache.org; Tue, 02 Jul 2002 20:33:16 +0900 Received: from [61.119.142.233] (helo=mega-bucks.co.jp) by mail2.jp.viruscheck.net with esmtp (Exim 3.20 #2) id 17PLv4-000236-00 for users@httpd.apache.org; Tue, 02 Jul 2002 20:34:06 +0900 Message-ID: <3D218EF1.5080605@mega-bucks.co.jp> Date: Tue, 02 Jul 2002 20:30:57 +0900 From: Jean-Christian Imbeault User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2 X-Accept-Language: en-us MIME-Version: 1.0 To: users@httpd.apache.org Subject: Re: ErrorDocument: 403 Forbidden error References: <14D1193E30E0894D8A773957C0AEE24AAA8BAD@SOMEXEVS001.ex.ordersx.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Boyle Owen wrote: >As far as I can see, your scheme only allows access to your site if the referer field contains your site name. > Oops. My mistake. The is a second SetEnvIf that allows for my main site to access this server (which contains all no html resources, images, cgi's, etc...). If a user accesses an HTML page on the main server all the images (for example) point to this server. The images get served up since I allow for things to be served up if they contain this server's name (actually ip) or my main site's name. >Therefore, I don't see how any primary request (typed into the browser) can get access since it will have referer empty. You are right. And in that case I want my custom 403 error page to be served. I.e. if the referrer filed is blank serve up my custom error page. >>I think not. Since document root points to /www/htdocs using a leading / >>in "/error403.html" means from the DocumentRoot find error403.html. >> > >Exactly. So it should look for /www/htdocs/error403.html. Why do you say "I think not"? > I misread your original sentence. You are right, the document itself physically resides at /www/htdocs/error403.html and the directive is ErrorDocument 403 /error403.html Still, if I don't explicitly giving access to this file then I get the previously mentioned Apache error. Why do I need to explicitly give access to the file? Jc > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org