1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
<title>YaCy '#[clientname]#': Settings</title>
#[metas]#
</head>
<body marginheight="0" marginwidth="0" leftmargin="0" topmargin="0">
#[header]#
<br><br>
<h2>Settings</h2>
<p>This is the configuration page for YaCy. Access to this page should be limited to an administration person only.
To restrict the access to this page, please set an administrator account and password <a href="#admin">below.</a></p>
<p>If you want to restore all settings to the default values,
but <b>forgot your administration password</b>, you must stop the proxy,
delete the file 'DATA/SETTINGS/httpProxy.conf' in the YaCy application root folder and start YaCy again.
<p>
<table>
<tr>
<td><img src="env/grafics/down.gif" alt="down"><a href="#admin">Administration Account Settings</a></td>
<td rowspan="5" width="30"> </td>
<td><img src="env/grafics/down.gif" alt="down"><a href="#ServerAccess">Server Access Settings</a></td>
</tr>
<tr>
<td><img src="env/grafics/down.gif" alt="down"><a href="#general">General Settings</a></td>
<td><img src="env/grafics/down.gif" alt="down"><a href="#SystemBehaviour">System Behaviour Settings</a></td>
</tr>
<tr>
<td><img src="env/grafics/down.gif" alt="down"><a href="#ProxyAccess">Server Access Settings</a></td>
<td><img src="env/grafics/down.gif" alt="down"><a href="#seed">Seed Upload Settings</a></td>
</tr>
<tr>
<td><img src="env/grafics/down.gif" alt="down"><a href="#http">HTTP Networking</a></td>
<td><img src="env/grafics/down.gif" alt="down"><a href="#messageForwarding">Message Forwarding (optional)</a></td>
</tr>
<tr>
<td><img src="env/grafics/down.gif" alt="down"><a href="#proxy">Remote Proxy (optional)</a></td>
<td><img src="env/grafics/down.gif" alt="down"><a href="#parser">Content Parser Settings</a></td>
</tr>
<tr>
<td><img src="env/grafics/down.gif" alt="down"><a href="#portForwarding">Port Forwarding (optional)</a></td>
<td> </td>
</tr>
</table>
</p>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="admin">Administration Account Settings</legend>
<p>This is the account that restricts access to this 'Settings' page. If you have not customized it yet, you should do so now:
<p><table border="0" cellspacing="5">
<tr valign="top">
<td>Account Name:</td><td><input name="adminuser" type="text" size="16" maxlength="16" value="#[adminuser]#"></td>
</tr>
<tr valign="top">
<td>Password:</td>
<td><input name="adminpw1" type="password" size="16" maxlength="16" value=""></td></tr>
<tr valign="top">
<td>Password (repeat same as above):</td>
<td><input name="adminpw2" type="password" size="16" maxlength="16" value=""></td>
</tr>
<tr valign="top">
<td colspan="2"><input type="submit" name="adminaccount" value="submit"></td>
</tr>
</table>
</fieldset>
</form><br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="general">General Settings</legend>
<p>
<table border="0" cellspacing="5">
<tr valign="top">
<td>Peer Name:</td>
<td><input name="peername" type="text" size="32" maxlength="80" value="#[peerName]#"></td>
<td><b>Your peer name defines also a new '.yacy' - domain, which can be accessed from every peer running this proxy.</b>
Using your 'Home Page' and 'File Share' - zones you also have a platform to provide content to your new domain.<br>
<i>(hint: Choose a name that appears on a web page that tells something about you, visit the page, get the 'senior' status, and you can be found...)</i></td>
</tr>
<tr valign="top">
<td>staticIP (optional):</td>
<td><input name="staticIP" type="text" size="32" maxlength="80" value="#[staticIP]#"></td>
<td><b>The staticIP can help that your peer can be reached by other peers in case that your
peer is behind a firewall or proxy.</b> You can create a tunnel through the firewall/proxy
(look out for 'tunneling through https proxy with connect command') and create
an access point for incoming connections.
This access address can be set here (either as IP number or domain name).
If the address of outgoing connections is equal to the address of incoming connections,
you don't need to set anything here, please leave it blank.<br>
</tr>
<tr valign="top">
<td colspan="3"><input type="submit" name="generalsettings" value="submit"></td>
</tr>
</table>
</fieldset>
</form><br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="ProxyAccess">Server Access Settings</legend>
These settings configure the access method to your own http proxy and server.
All traffic is routed throug one single port, for both proxy and server.<br>
<br><b>Port Configuration</b><br><br>
<table border="0" cellspacing="5">
<tr valign="top">
<td>Proxy and http-Server Administration Port:</td>
<td><input name="port" type="text" size="5" maxlength="5" value="#[port]#"></td>
<td><i>Changes will take effect after restart only.</i></td>
</tr>
</table>
<p><b>Server Access Restrictions</b><br><br>You can restrict the access to this proxy/server using a two-stage security barrier:
<ul>
<li>define an <i>access domain</i> with a list of granted client IP-numbers or with wildcards</li>
<li>define an <i>user account</i> with an user:password - pair</li>
</ul><br>
<p>This is the account that restricts access to the proxy function. You probably don't want to share the proxy to the internet, so you should set the IP-Number Access Domain to a pattern that corresponds to you local intranet. The default setting should be right in most cases. If you want, you can also set a proxy account so that every proxy user must authenticate first, but this is rather unusual.</p>
<p>
<table border="0" cellspacing="5">
<tr valign="top">
<td>IP-Number filter:</td>
<td colspan ="2"><input name="proxyfilter" type="text" size="50" maxlength="1000" value="#[proxyfilter]#"></td>
</tr>
<tr valign="top">
<td>Accounts:</td>
<td><input name="use_proxyaccounts" type="checkbox" size="16" maxlength="16" value="on" #(use_proxyAccounts)#::checked#(/use_proxyAccounts)#> Use <a href="User_p.html">Proxy Accounts</a></td>
</tr>
<tr valign="top">
<td colspan="2"><input type="submit" name="proxyaccount" value="Submit"></td>
</tr>
</table>
</fieldset>
</form><br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="http">HTTP Networking</legend>
<table border="0" cellspacing="5">
<tr valign="top">
<td>Transparent Proxy:</td>
<td><input type="checkbox" name="isTransparentProxy" align="top" #(isTransparentProxy)#::checked#(/isTransparentProxy)#></td>
<td>With this you can specify if YaCy can be used as transparent proxy.<br>
<i>Hint: On linux you can configure your firewall to transparently redirect all http traffic through yacy using this iptables rule:</i><br>
<small><code>iptables -t nat -A PREROUTING -p tcp -s 192.168.0.0/16 --dport 80 -j DNAT --to 192.168.0.1:#[port]#</code></small>
</td>
</tr>
<tr valign="top">
<td>Connection Keep-Alive:</td>
<td><input type="checkbox" name="connectionKeepAliveSupport" align="top" #(connectionKeepAliveSupport)#::checked#(/connectionKeepAliveSupport)#></td>
<td>With this you can specify if YaCy should support the HTTP connection keep-alive feature.</td>
</tr>
<tr valign="top">
<td colspan="3"><input type="submit" name="httpNetworking" value="submit"> <i>Changes will take effect immediately.</i></td>
</tr>
</table>
</fieldset>
</form><br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="proxy">Remote Proxy (optional)</legend>
<p>YaCy can use another proxy to connect to the internet. You can enter the address for the remote proxy here:</p>
<p><table border="0" cellspacing="5">
<tr valign="top">
<td>Remote proxy host:</td>
<td><input name="remoteProxyHost" type="text" size="32" maxlength="128" value="#[remoteProxyHost]#"></td>
</tr>
<tr valign="top">
<td>Remote proxy port:</td>
<td><input name="remoteProxyPort" type="text" size="5" maxlength="5" value="#[remoteProxyPort]#"></td>
</tr>
<tr valign="top">
<td>no-proxy adresses:</td>
<td><input name="remoteProxyNoProxy" type="text" size="32" maxlength="128" value="#[remoteProxyNoProxy]#"></td>
</tr>
<tr valign="top">
<td>Use remote proxy:</td>
<td><input type="checkbox" name="remoteProxyUse" align="top" #(remoteProxyUseChecked)#::checked#(/remoteProxyUseChecked)#></td>
</tr>
<tr valign="top">
<td colspan="2"><input type="submit" name="proxysettings" value="submit"> <i>Changes will take effect immediately.</i></td>
</tr>
</table>
</fieldset>
</form><br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="portForwarding">Port Forwarding (optional)</legend>
<p>You can use a remote server running a ssh demon to forward your server/proxy port.
This is useful if you want to tunnel throug a NAT/router.
Alternatively, you can simply set a virtual server port on your NAT/Server to enable connections from outside.</p>
<table border="0" cellspacing="5">
<tr valign="top">
<td>Enable port forwarding:</td>
<td><input type="checkbox" name="portForwardingEnabled" align="top" #(portForwardingEnabled)#::checked#(/portForwardingEnabled)#></td>
<td>Enabling disabling port forwarding via secure channel.</td>
</tr>
<tr valign="top">
<td>Forwarding via proxy:</td>
<td><input type="checkbox" name="portForwardingUseProxy" align="top" #(portForwardingUseProxy)#::checked#(/portForwardingUseProxy)# DISABLED></td>
<td><!-- Specifies if the connection should be established through the <a href="#proxy">remote proxy</a>.-->
<i>Function not available at the moment.</i></td>
</tr>
<tr valign="top">
<td>Forwarding port:</td>
<td><input name="portForwardingPort" type="text" size="5" maxlength="5" value="#[portForwardingPort]#"></td>
<td>The port on the remote server that should be forwarded via the secure channel to the local host.</td>
</tr>
<tr valign="top">
<td>Forwarding host:</td>
<td><input name="portForwardingHost" type="text" size="32" maxlength="128" value="#[portForwardingHost]#"></td>
<td> </td>
</tr>
<tr valign="top">
<td>Forwarding host port:</td>
<td><input name="portForwardingHostPort" type="text" size="5" maxlength="5" value="#[portForwardingHostPort]#"></td>
<td> </td>
</tr>
<tr valign="top">
<td>Forwarding host user:</td>
<td><input name="portForwardingHostUser" type="text" size="32" maxlength="128" value="#[portForwardingHostUser]#"></td>
<td> </td>
</tr>
<tr valign="top">
<td>Forwarding host password:</td>
<td><input name="portForwardingHostPwd" type="password" size="32" maxlength="128" value="#[portForwardingHostPwd]#"></td>
<td> </td>
</tr>
<tr valign="top">
<td colspan="3"><input type="submit" name="portForwarding" value="Submit"> <i>Changes will take effect immediately.</i></td>
</tr>
</table>
</fieldset>
</form><br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="ServerAccess">Server Access Settings</legend>
<p>Here you can restrict access to the server. By default, the access is not limited, because this function is needed to spawn the p2p index-sharing function. If you block access to your server (setting anything else than '*'), then you will also be blocked from using other peers' indexes for search service. However, blocking access may be correct in enterprise environments where you only want to index your company's own web pages.</p>
<p>ATTENTION: Your current IP is recognized as "#[clientIP]#". If the value you enter here does not match with this IP, you will not be able to access the server pages anymore</p>
<p>
<table border="0" cellspacing="5">
<tr valign="top">
<td>IP-Number filter:</td>
<td colspan ="2"><input name="serverfilter" type="text" size="50" maxlength="1000" value="#[serverfilter]#"></td>
</tr>
<!--
<tr valign="top">
<td>Account Name:</td><td><input name="serveruser" type="text" size="16" maxlength="16" value="#[serveruser]#"></td>
</tr>
-->
<tr valign="top">
<td valign="bottom" rowspan="3"><input type="submit" name="serveraccount" value="Submit"></td>
</tr>
<!--
<tr valign="top"><td>Password:</td><td><input name="serverpw1" type="password" size="16" maxlength="16" value=""></td></tr>
<tr valign="top"><td>Password (repeat same as above):</td><td><input name="serverpw2" type="password" size="16" maxlength="16" value=""></td></tr>
-->
</table>
</fieldset>
</form><br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="SystemBehaviour">System Behaviour Settings</legend>
<table>
<tr><td>Auto pop-up of status page on start-up:</td>
<td><input type="submit" name="enpop" value="enable"> / <input type="submit" name="dispop" value="disable"></td></tr>
</table>
</fieldset>
</form><br>
<p>
<fieldset>
<legend id="seed">Seed Upload Settings</legend>
<p>With these settings you can configure if you have an account on a public accessible
server where you can host a seed-list file.</p>
<p><b>General Settings:</b></p>
If you enable one of the available uploading methods, you will become a principal peer.
Your peer will then upload the seed-bootstrap information periodically,
but only if there had been changes to the seed-list.
</p>
<form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<table border="0" cellspacing="5">
<tr valign="top">
<td>Upload Method:</td>
<td><select name="seedUploadMethod" size="1">
#{seedUploadMethods}#
<option value="#[name]#" #(selected)#::selected#(/selected)#>#[name]#</option>
#{/seedUploadMethods}#
</select>
<input type="submit" name="seedUploadRetry" value="Retry Uploading"></td>
<td><i>Here you can specify which upload method should be used. Select 'none' to deactivate uploading.</i></td>
</tr>
<tr valign="top">
<td>URL:</td>
<td><input name="seedURL" type="text" size="40" value="#[seedURL]#"></td>
<td><i>The URL that can be used to retrieve the uploaded seed file, like
http://www.<my-host>.net/yacy/seed.txt'</i></td>
</tr>
<tr>
<td colspan="3"><input type="submit" name="seedSettings" value="submit"></td>
</tr>
</table>
</form>
#{seedUploadMethods}#
#%[file]%#
#{/seedUploadMethods}#
</fieldset>
<br>
<p><form action="SettingsAck_p.html" method="post" enctype="multipart/form-data">
<fieldset><legend id="messageForwarding">Message Forwarding</legend>
<p>With this settings you can activate or deactivate forwarding of yacy-messages via email.
<p>
<table border="0" cellspacing="5">
<tr valign="top">
<td>Enable message forwarding:</td>
<td><input type="checkbox" name="msgForwardingEnabled" align="top" #(msgForwardingEnabled)#::checked#(/msgForwardingEnabled)#></td>
<td><i>Enabling/Disabling message forwarding via email.</td>
</tr>
<tr valign="top">
<td>Forwarding Command:</td>
<td><input name="msgForwardingCmd" type="text" size="32" value="#[msgForwardingCmd]#"></td>
<td><i>The command-line program that should be used to forward the message.<br>e.g.:</i> <code>/usr/sbin/sendmail</code></td>
</tr>
<tr valign="top">
<td>Forwarding To:</td>
<td><input name="msgForwardingTo" type="text" size="32" maxlength="128" value="#[msgForwardingTo]#"></td>
<td><i>The recipient email-address.<br> e.g.:</i> <code>root@localhost</code></td>
</tr>
<tr valign="top">
<td colspan="3"><input type="submit" name="msgForwarding" value="submit"> <i>Changes will take effect immediately.</i></td>
</tr>
</table>
</fieldset>
</form><br>
<br>
<p><form action="SettingsAck_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>
For a detailed description of the various MIME-types take a look at <a href="http://www.iana.org/assignments/media-types/">http://www.iana.org/assignments/media-types/</a></p>
<p>
<table border="0" cellpadding="2" cellspacing="1">
<tr class="TableHeader" valign="bottom">
<td class="small" >Activate</td>
<td class="small" >Mime-Type</td>
<td class="small" >Parser Class Name</td>
<td class="small" ></td>
</tr>
#{parser}#
<tr class="TableCellDark">
<td class="small" align="center"><input type="checkbox" name="#[mime]#" align="top" #(status)#::checked#(/status)#></td>
<td class="small" >#[mime]#</td>
<td class="small" title="Full qualified name: #[name]#">#[shortname]#</td>
<td class="small" width="100%"></td>
</tr>
#{/parser}#
<tr class="TableCellLight">
<td class="small" align="center"><input type="checkbox" name="allParserEnabled" align="top" #(allParserEnabled)#::checked#(/allParserEnabled)#>
<td colspan="2" class="small" >Enable all parsers</td>
<td class="small"> </td>
</tr>
<tr class="TableCellLight">
<td colspan="4" class="small" ><input type="submit" name="parserSettings" value="submit"> Changes take effect immediately</td>
</tr>
</table>
</fieldset>
</form><br>
#[footer]#
</body>
</html>
|
