##########################################################
#
-# No-Such-Domain Error Output template for Privoxy.
+# Feature disabled or referrer untrusted Error Output template for Privoxy.
#
#
# USING HTML TEMPLATES:
#
# Template files are written win plain HTML, with a few
# additions:
-#
+#
# - Lines that start with a '#' character like this one
# are ignored
#
# strings @if-<name>start and if-<name>-end@. The strings
# should be placed in HTML comments (<!-- -->), so the
# html structure won't be messed when the magic happens.
-#
+#
# USABLE SYMBOLS IN THIS TEMPLATE:
# --------------------------------
#
# my-hostname:
# The hostname associated with my-ip-addr
# admin-address:
-# The email address of the pxoxy's administrator, as configured
+# The email address of the proxy administrator, as configured
# in the config file
# default-cgi:
# The URL for the "main menu" builtin CGI of this proxy
# The development status of the proxy software: "alpha", "beta",
# or "stable".
# homepage:
-# The URL of the SourceForge ijbswa project, who maintains this
-# software.
+# The URL of the Privoxy project, which maintains this software.
#
# CONDITIONAL SYMBOLS FOR THIS TEMPLATE AND THEIR DEPANDANT SYMBOLS:
# ------------------------------------------------------------------
# unstable:
# this is an alpha or beta release of the proxy software
# have-adminaddr-info:
-# An e-mail address for the local Privoxy adminstrator has
+# An e-mail address for the local Privoxy administrator has
# been specified and is available through the "admin-address"
# symbol
# have-proxy-info:
<title>Configuration Page Disabled</title>
<meta http-equiv="Content-Style-Type" content="text/css">
<meta http-equiv="Content-Script-Type" content="text/javascript">
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="robots" content="noindex,nofollow">
<link rel="stylesheet" type="text/css" href="@default-cgi@send-stylesheet">
+ <link rel="shortcut icon" href="@default-cgi@error-favicon.ico">
</head>
<body>
- <table cellpadding="20" cellspacing="10" border="0" width="100%">
+ <table summary="" cellpadding="20" cellspacing="10" border="0" width="100%">
<tr>
<td class="title">
<tr>
<td class="warning">
- <h2>Privoxy Configuration page diasabled</h2>
- <p>The Privoxy administrator has decided to disable this
- feature. If you want to use it, you must ask them to
- enable it.</p>
- <p>If you are the Privoxy administrator, you can enable
- this feature by changing the appropriate line in your
- configuration file.</p>
+ <h2>Privoxy Configuration access denied</h2>
+ <p>Access to <b>@url@</b> has been denied because:</p>
+
+ <ul>
+ <li>it requires a feature that has been disabled by the Privoxy administrator,</li>
+ <li>you didn't come here through one of Privoxy's CGI pages, or</li>
+ <li>the <q>Referer:</q> header is blocked.</li>
+ </ul>
+
+ <p>Note that the following features which used to be enabled in earlier
+ releases are now off by default:
+ </p>
+ <ul>
+ <li><a href="@user-manual@config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a></li>
+ <li><a href="@user-manual@config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a></li>
+ <li><a href="@user-manual@config.html#ENABLE-REMOTE-HTTP-TOGGLE">enable-remote-http-toggle</a>
+ (Most likely you don't need this anyway.)</li>
+ </ul>
+
+ <p>Please refer to the documentation behind the links to learn how to
+ enable them again and what the consequences are.</p>
+
+ <p>All enabled features are accessible from the
+ <a href="@default-cgi@">main menu</a>, some of them
+ are <em>protected</em> with a referrer check though.
+ If you got caught by the referrer check, but are <strong>absolutely</strong> sure
+ you know what you are doing, please <a title="Retry from a trusted referrer"
+ href="@url@">try again</a>.</p>
+
+ <p>If the <q>Referer:</q> header is blocked, you'll have to make an exception for
+ Privoxy's web interface first. Note that <em>dumb</em> referrer blocking
+ is a bad idea anyway, as it makes it easier to fingerprint your
+ requests. Consider using Privoxy's conditional referrer block instead.</p>
</td>
</tr>
<tr>
<td class="box">
<h2>More Privoxy:</h2>
- <ul>@menu@</ul>
+ <ul>@menu@<li><a href="@user-manual@">Documentation</a></li></ul>
</td>
</tr>
+<!-- @if-have-help-info-start -->
<tr>
<td class="info">
-#include mod-support-and-service
+#include mod-local-help
</td>
</tr>
+<!-- if-have-help-info-end@ -->
-<!-- @if-have-help-info-start -->
<tr>
<td class="info">
-#include mod-local-help
+#include mod-support-and-service
</td>
</tr>
-<!-- if-have-help-info-end@ -->
-
- <tr>
- <td>
- <p class="small">Valid <a href="http://validator.w3.org/">HTML 4.01 Strict</a></p>
- </td>
- </tr>
</table>
projects / privoxy.git / blobdiff