From nobody@hyperreal.com Mon Apr 28 10:20:48 1997 Received: (from nobody@localhost) by hyperreal.com (8.8.5/8.8.5) id KAA09834; Mon, 28 Apr 1997 10:20:48 -0700 (PDT) Message-Id: <199704281720.KAA09834@hyperreal.com> Date: Mon, 28 Apr 1997 10:20:48 -0700 (PDT) From: David Kozinn Reply-To: dkozinn@csc.com To: apbugs@hyperreal.com Subject: Allow customized messages for ProxyBlock X-Send-Pr-Version: 3.2 >Number: 494 >Category: mod_proxy >Synopsis: Allow customized messages for ProxyBlock >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: change-request >Submitter-Id: apache >Arrival-Date: Mon Apr 28 10:30:01 1997 >Last-Modified: Mon Apr 28 17:30:26 PDT 1997 >Originator: dkozinn@csc.com >Organization: >Release: 1.2b8 >Environment: >Description: The current implementation of ProxyBlock sends a hard-coded message back when an attempt is made to access a restricted site. I'd like to be able to (at minimum) substitute my own message there, and optimally be able to use the full error message functionality (such as to log the attempt to a special file, send someone email, etc.) >How-To-Repeat: Implement proxy caching, block a site, try to access it. The error that comes back is fixed, there is no way (short of modification to the source code to change it. >Fix: Add in a ProxyError directive similar to the ErrorDocument directive >Audit-Trail: State-Changed-From-To: open-suspended State-Changed-By: chuck State-Changed-When: Mon Apr 28 17:22:44 PDT 1997 State-Changed-Why: Thanks for the suggestion. We'll consider this for 1.2.1; we're in feature freeze for 1.2.0. State-Changed-From-To: suspended-closed State-Changed-By: chuck State-Changed-When: Mon Apr 28 17:30:26 PDT 1997 State-Changed-Why: Duplicate of PR #362. >Unformatted: