From d8c3628ce4a3e4fee2d5dd023c2b4e5188c5ad16 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Mon, 22 Jan 2007 15:15:08 +0000 Subject: [PATCH] - Be a bit more descriptive about why CGI access has been denied and what the user can do about it. - Add a "go there anyway" link to pass the referrer check. - Add empty table summary to silence validator warning. - Remove the useless W3C validator link. --- templates/cgi-error-disabled | 31 +++++++++++++++++++------------ 1 file changed, 19 insertions(+), 12 deletions(-) diff --git a/templates/cgi-error-disabled b/templates/cgi-error-disabled index 74d553b9..1a64b883 100644 --- a/templates/cgi-error-disabled +++ b/templates/cgi-error-disabled @@ -1,6 +1,6 @@ ########################################################## # -# No-Such-Domain Error Output template for Privoxy. +# Feature disabled or referrer untrusted Error Output template for Privoxy. # # # USING HTML TEMPLATES: @@ -79,7 +79,7 @@ - +

@@ -136,12 +149,6 @@ - - - -

@@ -102,12 +102,25 @@

Privoxy Configuration access denied

The feature you are trying to access has either been disabled - by the Privoxy administrator, or you came here by following an - unsafe external link.

Access to @url@ has been denied because:

+ +

it requires a feature that has been disabled by the Privoxy administrator,
you didn't come here through one of Privoxy's CGI pages, or
the Referer: header is blocked.

All enabled features are accessible from the - main menu.

+ main menu, some of them + are protected with a referrer check though. + If you got caught by the referrer check, but are absolutely sure + you know what you are doing, please try again.

+ +

If the Referer: header is blocked, you'll have to make an exception for + Privoxy's web interface first. Note that dumb referrer blocking + is a bad idea anyway, as it makes it easier to fingerprint your + requests. Consider using Privoxy's conditional referrer block instead.

Valid HTML 4.01 Strict

-- 2.39.2