make ConfigParser a protected page, for consistent behavior of locked

menu items.
pull/110/head
reger 8 years ago
parent f85aaa7c76
commit a011a97de9

@ -18,7 +18,7 @@
#%env/templates/header.template%#
#%env/templates/submenuCrawler.template%#
<h2>Parser Configuration</h2>
<form id="parsersettings" action="ConfigParser.html" method="post" enctype="multipart/form-data">
<form id="parsersettings" action="ConfigParser_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="parser">Content Parser Settings</legend>
<p>
With this settings you can activate or deactivate parsing of additional content-types based on their MIME-types.<br />

@ -35,7 +35,7 @@ import net.yacy.server.serverObjects;
import net.yacy.server.serverSwitch;
public class ConfigParser {
public class ConfigParser_p {
public static serverObjects respond(final RequestHeader header, final serverObjects post, final serverSwitch env) {
// return variable that accumulates replacements
@ -44,11 +44,6 @@ public class ConfigParser {
if (post != null) {
if (!sb.verifyAuthentication(header)) {
// force log-in
prop.authenticationRequired();
return prop;
}
if (post.containsKey("parserSettings")) {
post.remove("parserSettings");

@ -2,6 +2,6 @@
<h3>Load Web Pages</h3>
<ul class="SubMenu">
<li><a href="CrawlStartSite.html" class="MenuItemLink">Site Crawling</a></li>
<li><a href="ConfigParser.html" class="MenuItemLink #(authorized)#lock::unlock#(/authorized)#">Parser Configuration</a></li>
<li><a href="ConfigParser_p.html" class="MenuItemLink #(authorized)#lock::unlock#(/authorized)#">Parser Configuration</a></li>
</ul>
</div>
Loading…
Cancel
Save