- <td bgcolor=#eeeeee>
- <h2>Foobar Configuration page diasabled</h2>
- <blockquote>
- <p>The Foobar 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 Foobar administrator, you can enable
- this feature by changing the appropriate line in your
- configuration file.</p>
- </blockquote>
+ <td class="warning">
+ <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>