[freenet-cvs] r19060 - trunk/website/pages/en

[NEOatNHNG at freenetproject.org]

Author: NEOatNHNG
Date: 2008-04-06 20:05:09 +0000 (Sun, 06 Apr 2008)
New Revision: 19060

Modified:
   trunk/website/pages/en/Freeplot.php
   trunk/website/pages/en/applications.php
   trunk/website/pages/en/architecture.php
   trunk/website/pages/en/connect.php
   trunk/website/pages/en/documentation.php
   trunk/website/pages/en/donate.php
   trunk/website/pages/en/download-old.php
   trunk/website/pages/en/faq.php
   trunk/website/pages/en/fcp.php
   trunk/website/pages/en/fcptools.php
   trunk/website/pages/en/fphowto.php
   trunk/website/pages/en/freeapps.php
   trunk/website/pages/en/freemail.php
   trunk/website/pages/en/frost.php
   trunk/website/pages/en/install.php
   trunk/website/pages/en/keys.php
   trunk/website/pages/en/lists.php
   trunk/website/pages/en/mailsum.php
   trunk/website/pages/en/mailsum0104.php
   trunk/website/pages/en/mailsum0204.php
   trunk/website/pages/en/mailsum0304.php
   trunk/website/pages/en/mailsum0404.php
   trunk/website/pages/en/mailsum1103.php
   trunk/website/pages/en/mailsum1203.php
   trunk/website/pages/en/metadata.php
   trunk/website/pages/en/oldtools.php
   trunk/website/pages/en/openjobs.php
   trunk/website/pages/en/papers.php
   trunk/website/pages/en/switches.php
   trunk/website/pages/en/tools.php
   trunk/website/pages/en/understand.php
   trunk/website/pages/en/unixhowto.php
   trunk/website/pages/en/whatsnew.php
Log:
Fix HTML in various english pages

Modified: trunk/website/pages/en/Freeplot.php
===================================================================
--- trunk/website/pages/en/Freeplot.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/Freeplot.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,6 +1,5 @@
-<h4><big style="font-weight: normal;"><big></big></big><big
- style="font-weight: bold;"><big>GnuPlot with FreeNet HOWTO</big></big></h4>
-</div>
+<h4><big style="font-weight: bold;">GnuPlot with FreeNet HOWTO</big></h4>
+
 Plotting data with GnuPlot is both fun and easy! Using it for Freenet
 development... well... the harder part is collecting all the numbers
 you want to chart. Graphing with gnuplot is the easy part.<span

Modified: trunk/website/pages/en/applications.php
===================================================================
--- trunk/website/pages/en/applications.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/applications.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -3,7 +3,7 @@
 </h1>
 <br/>A variety of people have written some excellent tools and clients for use with Freenet.
 <br/>
-<br/><h3>Freenet Publishing & Retrieval Tools
+<br/><h3>Freenet Publishing &amp; Retrieval Tools
 </h3>
 <br/><a class='wiki'  href='http://localhost:8888/SSK@M7yZgrl8gwtAe1xEcR5Xyv4tFsoPAgM/fiw/6//'><b>Freesite Insertion Wizard</b></a> <b><span style='color:#FF0000;'>You must be running Freenet for this link to work.</span></b>
 <br/>

Modified: trunk/website/pages/en/architecture.php
===================================================================
--- trunk/website/pages/en/architecture.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/architecture.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -17,8 +17,8 @@
 (except from your own node) invisible to you. The traffic routing algorithm is therefore only able to direct traffic to one 
 of the few nodes that you know of that it thinks is most able to find what you are looking for.
 </p>
+<p>
 The traffic is encrypted, so it is quite difficult for the nodes that you connect to to see what your Freenet-traffic
 consists of, but it is far from impossible. It is therefore important that you connect only to people you know. If
 that is not possible, then at least people you've talked to.
 </p>
-<p>

Modified: trunk/website/pages/en/connect.php
===================================================================
--- trunk/website/pages/en/connect.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/connect.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -36,6 +36,7 @@
 (except from your own node) invisible to you. The traffic routing algorithm is therefore only able to direct traffic to one 
 of the few nodes that you know of that it thinks is most able to find what you are looking for.
 </p>
+<p>
 The traffic is encrypted, so it is quite difficult for the nodes that you connect to to see what your Freenet-traffic
 consists of, but it is far from impossible. It is therefore important that you connect only to people you know. If
 that is not possible, then at least people you've talked to.

Modified: trunk/website/pages/en/documentation.php
===================================================================
--- trunk/website/pages/en/documentation.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/documentation.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -52,4 +52,4 @@
 It is a good source of information about all sorts of
 Freenet related issues.
 </li>
-
+</ul>

Modified: trunk/website/pages/en/donate.php
===================================================================
--- trunk/website/pages/en/donate.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/donate.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -36,7 +36,7 @@
 Amount:
 <p>
 <span style="{border:1px solid black}">&nbsp;$20 <input type="radio" name="a3" value="20.00"></span>&nbsp; 
-<span style="{border:1px solid black}">&nbsp;$10 <input type="radio" name="a3" checked="true" 
+<span style="{border:1px solid black}">&nbsp;$10 <input type="radio" name="a3" checked="checked" 
 value="10.00"></span>&nbsp; 
 <span style="{border:1px solid black}">&nbsp;$5 <input type="radio" name="a3" value="5.00"></span>&nbsp;
 </p>

Modified: trunk/website/pages/en/download-old.php
===================================================================
--- trunk/website/pages/en/download-old.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/download-old.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,9 +1,9 @@
 <body><h2>Download Freenet 0.5</h2>
 
-<small><p>
+<p><small>
 Note that Freenet 0.5 is no-longer well supported as development effort has shifted to Freenet 0.7,
 which you can download from <a href="/download.html">here</a>.
-</p></small>
+</small></p>
 
 <h3>Important note for first time users</h3>
 
@@ -72,8 +72,7 @@
 freenet/ directory.
 <p>
 To see the latest changes of the builds in the stable branch, you can go to the
-<b><a
-href="/whatsnew.html">Changelog</b></a>.
+<b><a href="/whatsnew.html">Changelog</a></b>.
 
 
 <BR>&nbsp;<BR>

Modified: trunk/website/pages/en/faq.php
===================================================================
--- trunk/website/pages/en/faq.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/faq.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -272,13 +272,13 @@
 fproxy.bindTo=127.0.0.1,192.168.1.1<br>
 fproxy.allowedHosts=127.0.0.1,192.168.1.0/24<br>
 </code>
-<p>And if you want to grant full access (i.e. change config settings, restart, etc) to the node (WARNING: Be very careful who you give full fproxy access to!):</p>
+<p>And if you want to grant full access (i.e. change config settings, restart, etc) to the node (WARNING: Be very careful who you give full fproxy access to!):
 <code>
 fproxy.allowedHostsFullAccess=127.0.0.1,192.168.1.0/24<br>
 </code>
 </p>
 
-</p><p><b id="fec">What is FEC?</b><br>
+<p><b id="fec">What is FEC?</b><br>
 FEC stands for Forward Error Correction.  When large files are inserted into Freenet, they are split into many small blocks -- this is called a <i>splitfile</i>.
 FEC adds redundant check blocks to a splitfile, so that if some of the
 blocks fall out of the network or can't be found, you might still be
@@ -312,7 +312,7 @@
 
 <p><b id="whatsnew">What's new? Is there a changelog?</b><br>
 On every new build, a brief summary of all the main changes is posted to the support and devl lists and the freenet-announce board on Frost.
-Alternatively for a much more detailed view, check <a href="http://cia.navi.cx/stats/project/freenet">the SVN logs</b></a>.
+Alternatively for a much more detailed view, check <a href="http://cia.navi.cx/stats/project/freenet">the SVN logs</a>.
 
 <p><b id="backtrace">Why are there so many messages in my logfile with a backtrace attached?</b><br>
 Fred (and freenet in general) are still very much in development, and if something goes wrong it's worthwhile
@@ -385,7 +385,7 @@
 Generally speaking, joining our IRC channel is a good idea : #freenet on irc.freenode.net</p>
 
 <p><b id="freenethelp">Is there a Help Site that goes deeper into the questions newbies may have about Freenet, and where people can contribute too?</b><br>
-You could have a look at <a href="http://wiki.freenetproject.org/">our wiki. There is also an older, largely unmaintained <a href="http://www.freenethelp.org">Freenet Help Site</a> wiki. You can contribute to both, since they are wiki's so most pages are editable.
+You could have a look at <a href="http://wiki.freenetproject.org/">our wiki</a>. There is also an older, largely unmaintained <a href="http://www.freenethelp.org">Freenet Help Site</a> wiki. You can contribute to both, since they are wiki's so most pages are editable.
 
 <p><b id="bugs">Where can I report bugs?</b><br>
 You can use our <a href="https://bugs.freenetproject.org/">bug tracking system</a> or send a mail to our <a href="/lists.html">development mailing list</a>.</p>

Modified: trunk/website/pages/en/fcp.php
===================================================================
--- trunk/website/pages/en/fcp.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/fcp.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -59,7 +59,7 @@
     </ul>
   </li>
 
-  <li><code>ClientGet</code></li>
+  <li><code>ClientGet</code>
   	<ul>
     <li><code>URIError</code></li>
     <li><code>Restarted</code></li>
@@ -68,8 +68,9 @@
     <li><code>DataFound</code></li>
         <li><code>DataChunk</code></li>
 	</ul>
+  </li>
 
-  <li><code>ClientPut</code></li>
+  <li><code>ClientPut</code>
   	<ul>
     <li><code>URIError</code></li>
     <li><code>Restarted</code></li>
@@ -78,21 +79,25 @@
     <li><code>Pending</code></li>
     <li><code>Success</code></li>
 	</ul>
+  </li>
 
-  <li><code>GenerateCHK</code></li>
+  <li><code>GenerateCHK</code>
   <ul>
 	<li><code>Success</code></li>
   </ul>
+  </li>
 
-  <li><code>GenerateSVKPair</code></li>
+  <li><code>GenerateSVKPair</code>
   <ul>
 	<li><code>Success</code></li>
   </ul>
+  </li>
 
-  <li><code>ClientDelete</code></li>
+  <li><code>ClientDelete</code>
   <ul>
 	<li><code>Success</code> </li>
   </ul>
+  </li>
 
   <li><code>InvertPrivateKey</code>
     <ul>

Modified: trunk/website/pages/en/fcptools.php
===================================================================
--- trunk/website/pages/en/fcptools.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/fcptools.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -183,4 +183,4 @@
   -f, --logfile file     Full pathname for the output log file
                          (default stdout)</pre>
 
-<p><h1>*</h1></p>
+<p></p><h1>*</h1>

Modified: trunk/website/pages/en/fphowto.php
===================================================================
--- trunk/website/pages/en/fphowto.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/fphowto.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,5 +1,5 @@
-<span style='color:blue'><h2>GnuPlot with FreeNet HOWTO</h2><p></span>
-
+<h2 style='color:blue'>GnuPlot with FreeNet HOWTO</h2>
+<p>
 Plotting data with GnuPlot is both fun and easy! Using it for Freenet
 development... well... the harder part is collecting all the numbers
 you want to chart. Graphing with gnuplot is the easy part.

Modified: trunk/website/pages/en/freeapps.php
===================================================================
--- trunk/website/pages/en/freeapps.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/freeapps.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,7 +1,6 @@
-<h1>Applications over Freenet
+<h1>Applications over Freenet</h1>
 
-</h1>
-<br/><b>Here you can share ideas about new applications that can run on top of Freenet. Before posting you should do a search on "Freenet" in <a class='wiki'  href='http://sourceforge.net/'>Sourceforge</a> to see if someone else hasn't already started a similiar project. <p>
+<br/><b>Here you can share ideas about new applications that can run on top of Freenet. Before posting you should do a search on "Freenet" in <a class='wiki'  href='http://sourceforge.net/'>Sourceforge</a> to see if someone else hasn't already started a similiar project. </b>
 <br/><b>Useful Links:</b>
 <br/>
 <br/>The spec of the <a href="/fcp.html">protocol</a> (FCP) which applications use to interact with Freenet - and all the other <a href="/docs.html">Developer documentation</a>.
@@ -46,7 +45,7 @@
 
 <br/>"So I decided to start work on a native Win32 Frost client (that I have named Flame). It won't have file exchange support but just really basic
 <br/>
-<br/>messaging functionality. I have been able to retrieve todays Freenet board Frost messages with it and read them in it (other boards should work too) but there are a few things to do (being able to write & insert messages and reply to messages in particular) but it is coming along nicely and I shall place it on the site once I have a more or less functional version up and running." ''(added by SebastianSpaeth - 22 Feb 2002)''
+<br/>messaging functionality. I have been able to retrieve todays Freenet board Frost messages with it and read them in it (other boards should work too) but there are a few things to do (being able to write &amp; insert messages and reply to messages in particular) but it is coming along nicely and I shall place it on the site once I have a more or less functional version up and running." ''(added by SebastianSpaeth - 22 Feb 2002)''
 <br/><hr/><a class='wiki'  href='http://eof.sourceforge.net/'><b>Everything Over Freenet</b></a>
 <br/>
 <br/>Everything Over Freenet (EOF) creates gateways for other protocols (such as SMTP) to work over Freenet.
@@ -62,6 +61,6 @@
 <br/><a class='wiki'  href='http://127.0.0.1:8888/SSK@txvIBhnrQG~BSKZ9C3U3pP9pjk4PAgM/flogger/1//'><b>Flogger</b></a> <b><span style='color:#FF0000;'>You must be running Freenet for this link to work</span></b>
 <br/>
 <br/>A Freenet community publication system. Currently in the planning stages.
-<br/>Email: <a class='wiki'  href='mailto:jrandom at cryptomail.org'>jrandom at cryptomail.org</a><br/></div>
+<br/>Email: <a class='wiki'  href='mailto:jrandom at cryptomail.org'>jrandom at cryptomail.org</a><br/>
 <p class="editdate">Last modification date: Tuesday 11 of February, 2003 [16:47:26] by mihi</p>
 

Modified: trunk/website/pages/en/freemail.php
===================================================================
--- trunk/website/pages/en/freemail.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/freemail.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -20,6 +20,7 @@
 <ul>
 <li>&lt;anything&gt;@[short Freemail-address].freemail</li>
 </ul>
+<p>
 After running the last command you now have a running Freemail proxy, listening on localhost at IMAP port 3143 for incoming mails, 
 and SMTP port 3025 for outgoing mails. Connect to it using your favourite email client software</p>
 
@@ -60,7 +61,7 @@
 Your Freemail address is: anything at DS3FG3R...SF6FHJ8YUK.freemail
 Generating cryptographic keypair (this could take a few minutes)...
 Account creation completed.
-Account created for john. You may now set a password with --passwd <password>
+Account created for john. You may now set a password with --passwd &lt;password&gt;
 </pre>
 
 <p>

Modified: trunk/website/pages/en/frost.php
===================================================================
--- trunk/website/pages/en/frost.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/frost.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -60,6 +60,7 @@
 in the appearing tab.
 </p>
 <h3>Further information</h3>
+<p>
 Additional information about Frost can be found in
 the mailing-list or on the official website:
 </p>

Modified: trunk/website/pages/en/install.php
===================================================================
--- trunk/website/pages/en/install.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/install.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -15,7 +15,7 @@
 <p>For a graphical installation you have to have:</p>
 <ul>
 <li>A working Java Runtime Environment,</li>
-<li>a downloaded copy of <a href="http://downloads.freenetproject.org/alpha/installer/new_installer.jar" alt="new_installer.jar">
+<li>a downloaded copy of <a href="http://downloads.freenetproject.org/alpha/installer/new_installer.jar">
 http://downloads.freenetproject.org/alpha/installer/new_installer.jar</a> and</li>
 <li>a working graphical user interface (GUI)</li>
 </ul>

Modified: trunk/website/pages/en/keys.php
===================================================================
--- trunk/website/pages/en/keys.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/keys.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -23,7 +23,7 @@
 <br/>This kind of key works somewhat like a PGP keypair. You give one of them (the public key) away, and the other (the private key) you must keep in secret, for you will use it to insert things inside your namespace.
 <br/><div class='simplebox' align='center'>
 <br/>Example: SSK at rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/TFE//
-<br/></div><br/></div>
+<br/></div><br/>
 <p class="editdate">Last modification date: Monday 10 of March, 2003 [12:34:02] by greycat</p>
 <br/>
 

Modified: trunk/website/pages/en/lists.php
===================================================================
--- trunk/website/pages/en/lists.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/lists.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -65,7 +65,7 @@
 (<a class='wiki'  href='http://archives.freenetproject.org/list/cvs.en.html'>archive</a>)
 <br />A read-only mailing list to which CVS checkins are mailed.  This will probably only be of interest to developers.
 <br />
-<br /><a class='wiki' href='http://emu.freenetproject.org/cgi-bin/mailman/listinfo/darknet-tools/'>Darknet-Tools<a> (<a 
+<br /><a class='wiki' href='http://emu.freenetproject.org/cgi-bin/mailman/listinfo/darknet-tools/'>Darknet-Tools</a> (<a 
 class='wiki' href='http://archives.freenetproject.org/list/darknet-tools.en.html'>archive</a>)
 <br />A mailing list to discuss and develop ways of extending the darknet while keeping it a darknet: 
 Instant messenger plugins, IRC plugins, email invitations, functionality in the node needed to 

Modified: trunk/website/pages/en/mailsum.php
===================================================================
--- trunk/website/pages/en/mailsum.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/mailsum.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,7 +1,5 @@
-<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
-<tr>
-<center><h2>Summary of some discussions on the maillist</h2>
-</center>
+
+<h2 style="text-align:center;">Summary of some discussions on the maillist</h2>
 <P>
 <BR>
 <P>
@@ -17,17 +15,3 @@
 </b></a></span><P>
 <LI> <span style='color:blue'><a href="http://www.freenetproject.org/index.php?page=mailsum0404"><b>April
 </b></a></span><P>
-
-
-</td>
-<tr>
-<td align="right" valign="bottom">
-<BR>
-<P>
-<BR>
-<P>
-<BR>
-<P>
-<BR>
-</td>
-

Modified: trunk/website/pages/en/mailsum0104.php
===================================================================
--- trunk/website/pages/en/mailsum0104.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/mailsum0104.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,13 +1,11 @@
-<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
-<tr>
-<center><h2>Summary of some discussions on the maillist</h2>
+<h2>Summary of some discussions on the maillist</h2>
 <P>
-<h3>January</h3></center>
+<h3>January</h3>
 <P>
 1) <span style='color:blue'><b>Rant
 </b></span><P>
 Newsbyte ranted:<br>
-<i>Well, this may be a bit off topic, but what the heck. 
+<div style="font-style:italic;">Well, this may be a bit off topic, but what the heck. 
 I've just been out with some friends, and, as always when we get moderately drunk, we talked about politics, religion, philosophy etc. (when we are real drunk or when no babes are present, we usually talk about sex ;-)
 <p>
 Well, anyhow, being all european, and all friends (birds of a feather) we fully agreed on a lot of topics. Israel, Iraq, USA, etc...opinions didn't differ much there. But then it came to a typical european concept of free speech, which, I presume, may strike USA-citizens as a bit weird. While, seen at large, we have the same concept of free speech as in the USA, this opinion, curiously, always seem to shift to a more restricted idea of free speech when it concerns things as racism. In this respect (one of the few, I might add), I think the usa concept of it is much more honest and fair. This has undoubtably to do with our historic heritage, notably WWII. 
@@ -25,7 +23,7 @@
 Yes, it's the potential of making the power that the government (and corporations, and, yes, my friends) seem to think they have the perogative of, to become totally obsolete, that made me interested in Freenet. With a system as Freenet (when it will be fully working ;-), they can shout and do all they want, my ideal of a free society with a free flow of opinions will be there (at least in cyberspace). There might be drawbacks, as with any technology (and it's consequences), but all by all, it's worth it. <p>
 /*end rant*/
 <p>
-</i>
+</div>
 <br>
 <p>
 Jay Oliveri gave his considerable input by stating that, indeed, it was completely off topic for the development list and that Newsbyte had furthered the argument for more restrictive posting to this list. To which Newsbyte responded he was glad it (the rant) had some use, followed by an emoticon that indicated a possible irony and a link to <a href="http://www.verbumvanum.org/shirky">www.verbumvanum.org/shirky</a>  (chapter 3). Toad gave a little input on the devl-list too, but his/the more important and thoughtfull responses were not done on the maillist.
@@ -38,18 +36,12 @@
 2) <span style='color:blue'><b>Re: Stable node performance and gradual decline
 </b></span><P>
 Niklas Bergh 'surprised' us with a graph:<br>
-<i>Also see <a href="http://iakin.poweruser.org/freenetstuff/bw2.jpg"> http://iakin.poweruser.org/freenetstuff/bw2.jpg</a> for a graph that clearly indicates the gradual decline between the 15:th and most of the 18:th (actually there was an OOM generated the 18:th which killed the node). The graph also includes a slight preview of the result of some recent speed enhancements/locking changes (not present in stable code yet). 
+<div style="font-style:italic;">Also see <a href="http://iakin.poweruser.org/freenetstuff/bw2.jpg"> http://iakin.poweruser.org/freenetstuff/bw2.jpg</a> for a graph that clearly indicates the gradual decline between the 15:th and most of the 18:th (actually there was an OOM generated the 18:th which killed the node). The graph also includes a slight preview of the result of some recent speed enhancements/locking changes (not present in stable code yet). 
 <p>
-</i>
+</div>
 There was no response within the thread, probably because all could fully agree with the conclusion the current network works like crap.
 
 <p>
-
-
-
-</td>
-<tr>
-<td align="right" valign="bottom">
 <BR>
 <P>
 <BR>
@@ -58,5 +50,3 @@
 <P>
 <BR>
 Donation inquiries please contact <a href="mailto:ian at locut.us">Ian Clarke</a><BR>
-</td>
-

Modified: trunk/website/pages/en/mailsum0204.php
===================================================================
--- trunk/website/pages/en/mailsum0204.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/mailsum0204.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,13 +1,11 @@
-<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
-<tr>
-<center><h2>Summary of some discussions on the maillist</h2>
+<h2>Summary of some discussions on the maillist</h2>
 <P>
-<h3>February</h3></center>
+<h3>February</h3>
 <P>
 1) <span style='color:blue'><b>Freenet User Interface
 </b></span><P>
 Ian said:<br>
-<i>
+<div style="font-style:italic;">
 <p>
 I really want to tackle the issue of Freenet's user friendliness (or 
 lack thereof) head on.
@@ -68,7 +66,7 @@
 Having said that, don't worry too much, giving up one's social life to work on Freenet seems to come naturally after a while anyway.<p>
 Ian.
 <p>
-</i>
+</div>
 <br>
 <p>
 As usual, toad was sceptic about it, asking what exactly did this gave us and stating that substituting variables is trivial, and we already have it. However, he was a bit more enthousiastic about JMX as a possibility, as Iakin had pointed out in an earlier post. Ian responded with explaining that FreeMarker allows you to completely separate the data itself, from how you present that data. And that this is simply not even nearly possible with the current primitive variable substitution template mechanism. Toad apparently had no idea what that (or something else - a bold remark by Ian at the end, perhaps?) meant. Also, Ian had no clue what JMX meant, to the surprise of  Niklas, who explained it to him a zillion times before. Niklas, lastly, repeated that JMX stands for Java Management eXtenstion and provided some links: http://article.gmane.org/gmane.network.freenet.devel/5490 http://article.gmane.org/gmane.network.freenet.devel/5541 and  http://java.sun.com/products/JavaManagement/index.jsp . 
@@ -85,11 +83,6 @@
 
 <p>
 
-
-
-</td>
-<tr>
-<td align="right" valign="bottom">
 <BR>
 <P>
 <BR>
@@ -98,5 +91,5 @@
 <P>
 <BR>
 Donation inquiries please contact <a href="mailto:ian at locut.us">Ian Clarke</a><BR>
-</td>
 
+

Modified: trunk/website/pages/en/mailsum0304.php
===================================================================
--- trunk/website/pages/en/mailsum0304.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/mailsum0304.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,21 +1,19 @@
-<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
-<tr>
-<center><h2>Summary of some discussions on the maillist</h2>
+<h2>Summary of some discussions on the maillist</h2>
 <P>
-<h3>April</h3></center>
+<h3>April</h3>
 <P>
 1) <span style='color:blue'><b>wikiwiki? <a href="http://www.freenethelp.org">www.freenethelp.org</a>
 
 </b></span><P>
 Newsbyte said:<br>
-<i>
+<div style="font-style:italic;">
 <p>
 Made a first attempt to make my <a href="http://www.freenethelp.org">www.freenethelp.org</a> more wikish - for the moment only the main page. <br>
 Let me know what you think of it (if it's an improvement or not). <p>
 As millenia pass bye, more will become available. <p>
 Could be I will use something of Ian that he and I are discussing, if I ever figur out how to actually install and run it myself (which is not the case with the current wikish-thingy, btw).
 <p>
-</i>
+</div>
 <br>
 <p>
 A certain dude with the French-sounding name Anthony Le Mansec responded with saying that he was not keen on wikifarms like seedwiki, but he was convinced a wiki was really suitable for such a site, and would perfectly fit with freenet's philosophy. It would also be a target of choice for Wiki 'saboteurs', thus requiring a lot of time - at least until many users regurlarly "tend the garden".  Furthermore he suggested  the wiki Usemod.<p>
@@ -23,14 +21,14 @@
 
 Newsbyte's latest post about the subject was:
 <p>
-<i>Hi there, <br>
+<div style="font-style:italic;">Hi there, <br>
 I have slightly changed the <a href="http://www.freenethelp.org">www.freenethelp.org </a>site. Since some told me they found the login a hurdle for editing pages, and since the generic one had not much practical value, I've decide to drop it untill I can finetune it better. Added RecentChanges too, although in the beta-version of the prog it doesn't show the diff yet; hopefully this will become possible when it comes out of beta. <p>
 In any case, this is a new appeal for/to everyone that is somehow involved/knows about freenet to have a look and update the stuff. 
 But also for the newbies: feel free to give the site more structure and weed out spellingmistakes, etc. <p>
 For instance, the goal is to structure and mix together some of the ex-freesite-pages. Unofficial FAQ and Unoffical Anti-FAQ should become 'Ultimate FAQ' (already began with that), Freenet Explained and Freenet Explained2 should also be merged, etc. <p>
 If you have a free moment (and even if you don't ;-), go have a look and update where possible! The site is pretty well visited, so ppl are finding it usefull (or at least are curious), but the main prob is, that it's currently not very up-to-date, which could be frustrating, especially in the 'how to start' section or when trouble-shooting.<p> 
 Thus, pls, give it a try and edit/update! <p>
-Newsbyte</i>
+Newsbyte</div>
 
  
 
@@ -46,11 +44,6 @@
 
 <p>
 
-
-
-</td>
-<tr>
-<td align="right" valign="bottom">
 <BR>
 <P>
 <BR>
@@ -59,5 +52,3 @@
 <P>
 <BR>
 Donation inquiries please contact <a href="mailto:ian at locut.us">Ian Clarke</a><BR>
-</td>
-

Modified: trunk/website/pages/en/mailsum0404.php
===================================================================
--- trunk/website/pages/en/mailsum0404.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/mailsum0404.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,17 +1,15 @@
-<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
-<tr>
-<center><h2>Summary of some discussions on the maillist</h2>
+<h2>Summary of some discussions on the maillist</h2>
 <P>
-<h3>April</h3></center>
+<h3>April</h3>
 <P>
 <span style='color:blue'><b>RNFs still a problem?
 </b></span><P>
 Ian asked:<br>
-<i>
+<div style="font-style:italic;">
 <p>
 I am still seeing plenty of RNFs in 60067 (node has been up for a few hours and has been trying to do a splitfile download). Generally are other people still experiencing excessive RNFs? Under what circumstances? I would really like to get a better understanding of why they are happening. 
 <p>
-</i>
+</div>
 <br>
 <p>
 Malcolm handley responded by stating that he was seeing a lot of RNFs when inserting data. In a recent test that he did he got 48 RNFs in the course of inserting 30 4kb blocks. (He repeatedly tried to insert blocks until he had inserted the number that he wanted and recorded the number of errors that he got on the way.) He was not sure how many he was getting when requesting data at that moment, but it was also quite a few. Someone with the nick 'Someone' said he was not getting much RNFs. But when he got them it was almost always caused by nodes restarting (according to the RNF output).
@@ -20,9 +18,6 @@
 <br>
 <p>
 <p>
-</td>
-<tr>
-<td align="right" valign="bottom">
 <BR>
 <P>
 <BR>
@@ -31,5 +26,3 @@
 <P>
 <BR>
 Donation inquiries please contact <a href="mailto:ian at locut.us">Ian Clarke</a><BR>
-</td>
-

Modified: trunk/website/pages/en/mailsum1103.php
===================================================================
--- trunk/website/pages/en/mailsum1103.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/mailsum1103.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,23 +1,17 @@
-<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
-<tr>
-<center><h2>Summary of some discussions on the maillist</h2>
+<h2>Summary of some discussions on the maillist</h2>
 <P>
-<h3>November</h3></center>
+<h3>November</h3>
 <P>
 1) <span style='color:blue'><b>A really easy way to defeat datastore probing timingattacks?
 </b></span><P>
 Toad said:<br>
-<i>Ok, I had another crazy idea. This one is an idea to defeat the timing attacks we all know and hate. The attack goes like this: Request a file at HTL 0 from a node. The node has a 30% chance of forwarding the request to another node, if it doesn't have the file. The node returns the file quickly, and we conclude that the node must have the file in the store. Solutions to this basically involve making it look like the node didn't have the file. 
+<div style="font-style:italic;">Ok, I had another crazy idea. This one is an idea to defeat the timing attacks we all know and hate. The attack goes like this: Request a file at HTL 0 from a node. The node has a 30% chance of forwarding the request to another node, if it doesn't have the file. The node returns the file quickly, and we conclude that the node must have the file in the store. Solutions to this basically involve making it look like the node didn't have the file. 
 
 <p>One avenue of approach would be to try to emulate the slowness expected if we got the file from the next node on the chain. My suggestion: use the next node on the chain to emulate the latency of the next node on the chain! Send a special kind of request to the next node on the chain that requires it to route the request, return the datasource it would have routed to, and return the data we are sending to it. We would then send it back to the requestor in the usual way. An attacker who could surveil the network at an IP layer might be able to deduce we were sending it the data and it was returning us it through traffic analysis, but that is made harder by multiplexing, a reasonable traffic level, perhaps dividing the payload into several pieces and redirecting it through other nodes before it reaches the next node in the chain (in the hope of concealing it amidst regular traffic), or well known anti-traffic-analysis measures such as traffic padding. In any case it would be significantly better than we have now, at a moderate performance cost (it's only one extra hop in the base proposal). 
-<p>Thus the requesting node would not have a convincing case that we had the data in our store before they asked. Now, the question is, how important is our plausible deniability with respect to whether content was in our store before the request came in? Parts of freenet are designed to help this - for example the probabilistically not decrementing hops to live when HTL is low; but there are several ways to get around all these protections - requests at HTL 0 with timing information, announcements at HTL 0, and so on. If it is important, it may be possible to do something about it; if it is not, that may also make things easier. So, is it important?</i>
+<p>Thus the requesting node would not have a convincing case that we had the data in our store before they asked. Now, the question is, how important is our plausible deniability with respect to whether content was in our store before the request came in? Parts of freenet are designed to help this - for example the probabilistically not decrementing hops to live when HTL is low; but there are several ways to get around all these protections - requests at HTL 0 with timing information, announcements at HTL 0, and so on. If it is important, it may be possible to do something about it; if it is not, that may also make things easier. So, is it important?</div>
 <p>
 Some pointed out that a 'special request' could be used to determine that the node had the data, and was trying to conceil it. Newsbyte suggested that we could use the estimators for calculating the delay it would normally take, if  the node had to retrieve it from another node. Tom Kaitchuck and Martin Stone Davis had some objections to this, but seem to have thought that it was meant to be used for every node and/or with fixed time delays. However, Newsbyte pointed out that it should only be the node which has the data in it's store who would have to fake it, and that the estimator isn't fixed. Therefor, a request would only take on 'hop' longer, as Toad already indicated in his post. Toad, however, pointed out that the difficulty were the new nodes: since they have totally unrealistic estimators, it would be difficult to implement a time delay based on the estimators from the new nodes. Ofcourse, brandnew nodes would not have any data, but still, it could pose a problem. Luckily, he had some ideas to redress the problem, for instance, new node problem would be solved with estimators in the seednodes.
 
-
-</td>
-<tr>
-<td align="right" valign="bottom">
 <BR>
 <P>
 <BR>
@@ -26,5 +20,3 @@
 <P>
 <BR>
 Donation inquiries please contact <a href="mailto:ian at locut.us">Ian Clarke</a><BR>
-</td>
-

Modified: trunk/website/pages/en/mailsum1203.php
===================================================================
--- trunk/website/pages/en/mailsum1203.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/mailsum1203.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,13 +1,11 @@
-<table width="100%" border="0" cellspacing="0" cellpadding="0" height="100%">
-<tr>
-<center><h2>Summary of some discussions on the maillist</h2>
+<h2>Summary of some discussions on the maillist</h2>
 <P>
-<h3>December</h3></center>
+<h3>December</h3>
 <P>
 1) <span style='color:blue'><b>Multiplexing
 </b></span><P>
 Toad said:<br>
-<i>I am implementing multiplexing. This will bring significant benefits,
+<div style="font-style:italic;">I am implementing multiplexing. This will bring significant benefits,
 regardless of routing algorithm. The main ones:<p>
 
 * Dramatically reduced connection churn.<br>
@@ -19,7 +17,7 @@
   of dead code etc. Will be backwards compatible by using the old CH for
   the old Presentation.<br>
 * Protocol will be simpler to parse, resulting in fewer serious
-  (corruption -> connection death) bugs. Detecting where a trailer ended
+  (corruption -&gt; connection death) bugs. Detecting where a trailer ended
   etc is tricky on the old protocol. The new protocol will have an explicit
   trailer ended with code X command.<br>
 * Room for extensibility, can e.g. get rid of Identify message hack,
@@ -32,17 +30,11 @@
 
 I should have a prototype implementation running within a week or so..
 probably.
-</i>
+</div>
 <br>
 <p>
 Ian asked the question if it would solve the primary problem afflicting Freenet and thought it wouldn't... in which case he thought we shouldn't be focusing on that. Most others, such as Simon Porter and Niklas Bergh thought it was worthwhile, since it would yield benefits in any case, even if it wouldn't help with the routing (there was some discussion if MUX would directly benefit the routing or not). NG-routing wasn't being very effective as yet, and it wasn't clear exactly why not, so seen the limited resources of the project, most thought it was a good thing to persue multiplexing, and maybe go back to NG-routing later.
 
-
-
-
-</td>
-<tr>
-<td align="right" valign="bottom">
 <BR>
 <P>
 <BR>
@@ -51,5 +43,3 @@
 <P>
 <BR>
 Donation inquiries please contact <a href="mailto:ian at locut.us">Ian Clarke</a><BR>
-</td>
-

Modified: trunk/website/pages/en/metadata.php
===================================================================
--- trunk/website/pages/en/metadata.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/metadata.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -4,13 +4,14 @@
 <h2>Table of Contents</h2>
 <ul>
  <li> <a href="#Na3f">Overview</a></li>
- <li> <a href="#Na8c">Part Spec</a></li>
+ <li> <a href="#Na8c">Part Spec</a>
  <ul><li> <a href="#Na91">Redirect (CDC)</a></li>
      <li> <a href="#Na9f">DateRedirect (CDC)</a></li>
      <li> <a href="#Nae0">SplitFile (CDC)</a></li>
      <li> <a href="#Nb55">Info (MC)</a></li>
      <li> <a href="#Nb63">ExtInfo (MC)</a></li>
  </ul>
+ </li>
  <li> <a href="#Nb72">Examples</a></li>
  <li> <a href="#Nb9a">Handling Other Commands</a></li>
 </ul>
@@ -40,11 +41,11 @@
 part := "Document\n" [field ...] "EndPart\n"
 lastpart := "Document\n" [field ...] "End\n"
 field := KEY '=' VALUE '\n'
-KEY := <string not containing either '\n' or '='> 
+KEY := &lt;string not containing either '\n' or '='&gt; 
      //Heirarchical key name
-VALUE := <string not containing '\n'> 
+VALUE := &lt;string not containing '\n'&gt; 
      //value of the associated key
-REST := <arbitrary data of arbitrary length, not parsed by this parser> 
+REST := &lt;arbitrary data of arbitrary length, not parsed by this parser&gt; 
      //useful for XML metadata or other metadata not 
      //storable in the Info.* keyspace
 </pre>
@@ -179,7 +180,7 @@
 <br/>
 <br/><ul><li> The date format is in UNIX format - seconds from the epoch
 </li></ul>
-<ul><li> Only applies to KSKs and SSKs</a>
+<ul><li> Only applies to KSKs and SSKs
 </li></ul>
 <ul><li> The date must be taken UTC (TZ offset = 0)
 </li></ul>
@@ -208,10 +209,10 @@
 <br/>
 <br/><font face="courier" size="2">&nbsp;&nbsp;SplitFile.Size=&lt;hex&nbsp;file&nbsp;size&gt;
 </font><br/><font face="courier" size="2">&nbsp;&nbsp;SplitFile.BlockCount=&lt;hex&nbsp;no.&nbsp;of&nbsp;data&nbsp;blocks&gt;
-</font><br/><font face="courier" size="2">&nbsp;&nbsp;<a&nbsp;class='wiki'&nbsp;&nbsp;href='SplitFile.CheckBlockCount=&nbsp;&lt;hex.&nbsp;no&nbsp;of&nbsp;check&nbsp;blocks&gt;'>SplitFile.CheckBlockCount=&nbsp;&lt;hex.&nbsp;no&nbsp;of&nbsp;check&nbsp;blocks&gt;</a>
+</font><br/><font face="courier" size="2">&nbsp;&nbsp;<a class='wiki' href='SplitFile.CheckBlockCount=&nbsp;&lt;hex.&nbsp;no&nbsp;of&nbsp;check&nbsp;blocks&gt;'>SplitFile.CheckBlockCount=&nbsp;&lt;hex.&nbsp;no&nbsp;of&nbsp;check&nbsp;blocks&gt;</a>
 
 </font><br/><font face="courier" size="2">&nbsp;&nbsp;SplitFile.Block.&lt;n&gt;=&lt;URI&gt;
-</font><br/><font face="courier" size="2">&nbsp;&nbsp;<a&nbsp;class='wiki'&nbsp;&nbsp;href='SplitFile.Graph.&lt;x&gt;=&nbsp;a,b,c...'>SplitFile.Graph.&lt;x&gt;=&nbsp;a,b,c...</a>
+</font><br/><font face="courier" size="2">&nbsp;&nbsp;<a class='wiki' href='SplitFile.Graph.&lt;x&gt;=&nbsp;a,b,c...'>SplitFile.Graph.&lt;x&gt;=&nbsp;a,b,c...</a>
 </font><br/>
 <br/>
 <br/><ul><li> <a name="Naec"></a>0 &lt;= n &lt;= 65535
@@ -236,8 +237,8 @@
 </dd></dl><br/>
 <br/><h3><a name="Nb55">Info (MC) </a>
 </h3>
-<br/><font face="courier" size="2">&nbsp;&nbsp;&nbsp;<a&nbsp;class='wiki'&nbsp;&nbsp;href='Info.Format=&lt;string:&nbsp;MIME-type&gt;'>Info.Format=&lt;string:&nbsp;MIME-type&gt;</a>
-</font><br/><font face="courier" size="2">&nbsp;&nbsp;&nbsp;<a&nbsp;class='wiki'&nbsp;&nbsp;href='Info.Description=&lt;string:&nbsp;freeform&gt;'>Info.Description=&lt;string:&nbsp;freeform&gt;</a>
+<br/><font face="courier" size="2">&nbsp;&nbsp;&nbsp;<a class='wiki' href='Info.Format=&lt;string:&nbsp;MIME-type&gt;'>Info.Format=&lt;string:&nbsp;MIME-type&gt;</a>
+</font><br/><font face="courier" size="2">&nbsp;&nbsp;&nbsp;<a class='wiki' href='Info.Description=&lt;string:&nbsp;freeform&gt;'>Info.Description=&lt;string:&nbsp;freeform&gt;</a>
 </font><br/>
 <br/>The Info.* namespace is reserved for Dublin Core metadata.  Prepend "Info." to the keys you want to use to prevent collisions.  See http://www.freenetproject.org/doc/infometadata.html for details.
 <br/>
@@ -248,8 +249,8 @@
 <br/><h3><a name="Nb63">ExtInfo (MC)</a>
 </h3>
 <br/>
-<br/><font face="courier" size="2">&nbsp;&nbsp;<a&nbsp;class='wiki'&nbsp;&nbsp;href='ExtInfo.Trailing=yes'>ExtInfo.Trailing=yes</a>
-</font><br/><font face="courier" size="2">&nbsp;&nbsp;<a&nbsp;class='wiki'&nbsp;&nbsp;href='ExtInfo.URI=&lt;URI&gt;'>ExtInfo.URI=&lt;URI&gt;</a>
+<br/><font face="courier" size="2">&nbsp;&nbsp;<a class='wiki' href='ExtInfo.Trailing=yes'>ExtInfo.Trailing=yes</a>
+</font><br/><font face="courier" size="2">&nbsp;&nbsp;<a class='wiki' href='ExtInfo.URI=&lt;URI&gt;'>ExtInfo.URI=&lt;URI&gt;</a>
 </font><br/>
 <br/>
 <br/>If ExtInfo.Trailing is set to yes, the metadata for this file will include all data after the final "End" in the control document. If the ExtInfo.URI parameter exists, the contents of the URI pointed to should be included in the metadata for the current document.

Modified: trunk/website/pages/en/oldtools.php
===================================================================
--- trunk/website/pages/en/oldtools.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/oldtools.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -6,7 +6,7 @@
 <br /><p>
 <h3><a href="/fphowto.html">Development Aides</a></h3>
 <p>
-<br /><h3>Freenet Publishing & Retrieval Tools</h3>
+<br /><h3>Freenet Publishing &amp; Retrieval Tools</h3>
 
 <br /><a class='wiki'  href='http://127.0.0.1:8888/SSK@M7yZgrl8gwtAe1xEcR5Xyv4tFsoPAgM/fiw/9//'><b>Freesite Insertion Wizard</b></a> <b><span style='color:#FF0000;'>You must be running Freenet 0.5 for this link to work.</span></b>
 <br />

Modified: trunk/website/pages/en/openjobs.php
===================================================================
--- trunk/website/pages/en/openjobs.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/openjobs.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -11,7 +11,7 @@
 <P><LI>Spread the word, try to get Freenet in the news.
 <P><LI>Donate.
 <P><LI>Donate more.
-<P><LI>Help coding & debugging if you can.
+<P><LI>Help coding &amp; debugging if you can.
 <P><LI>Translate the web interface into your native language.
 <P><LI>Whine less about what's wrong with it, but give specific bug-reports in stead.
 <P><LI>Join #freenet on freenode for other suggestions/discussions.

Modified: trunk/website/pages/en/papers.php
===================================================================
--- trunk/website/pages/en/papers.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/papers.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -57,7 +57,7 @@
 Original white paper by Ian Clarke, Division of Informatics, University of Edinburgh 1999.
 </td></tr>
 </table>
-<br/
+<br/>
 <hr>
 <p>
 See also all the other <a href="http://wiki.freenetproject.org/FreenetSpecifications">Developer documentation</a>.<p>

Modified: trunk/website/pages/en/switches.php
===================================================================
--- trunk/website/pages/en/switches.php	2008-04-06 11:59:25 UTC (rev 19059)
+++ trunk/website/pages/en/switches.php	2008-04-06 20:05:09 UTC (rev 19060)
@@ -1,3 +1,776 @@
-<h2>Freenet Reference Daemon Documentation</h2> <h3>Fred,0.5,1.46,552</h3> <i>(This manual was automatically generated on Feb 5, 2003 1:16:03 PM. If you have updated Freenet since then, you may wish to regenerate it.)</i> FRED (Freenet REference Daemon) is the standard implementation of Freenet. This is the node, which serves as a router, data cache, and personal gateway all rolled into one. For FRED to run, it requires a configuration file to be present - this can be created either during the installation, by starting the node with the --config switch (see below), or running the freenet.config.Setup class manually. See the <a href="docs.html"> project documentation pages</a> for more information, or ask pointed and specific questions on the <a href="lists.html">mailing lists</a>. <h4>Command line switches: </h4> <table width="500" border="0" cellspacing="0" cellpadding="1"><tr><td><i>Name:</i></td><td><b>help</b>(--help | -h)</td></tr><tr><td><i>Arguments:</i></td><td></td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> prints this help message. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>system</b>(--system)</td></tr><tr><td><i>Arguments:</i></td><td></td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> prints JVM properties. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>version</b>(--version | -v)</td></tr><tr><td><i>Arguments:</i></td><td></td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> prints out version info. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>manual</b>(--manual)</td></tr><tr><td><i>Arguments:</i></td><td></td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> prints a manual in HTML. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>export</b>(--export | -x)</td></tr><tr><td><i>Arguments:</i></td><td>{file}|-</td></tr><tr><td><i>Default val:</i></td><td>-</td></tr><tr><td><i>Description:</i></td><td> exports a signed NodeReference. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>seed</b>(--seed | -s)</td></tr><tr><td><i>Arguments:</i></td><td>{file}|-</td></tr><tr><td><i>Default val:</i></td><td>-</td></tr><tr><td><i>Description:</i></td><td> seeds routing table with refs. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>config</b>(--config | -c)</td></tr><tr><td><i>Arguments:</i></td><td>{file}</td></tr><tr><td><i>Default val:</i></td><td>freenet.conf</td></tr><tr><td><i>Description:</i></td><td> generates or updates config file. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>paramFile</b>(--paramFile | -p)</td></tr><tr><td><i>Arguments:</i></td><td>{file}</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> path to a config file in a non-default location. </td></tr><tr><td colspan=2><hr></td></tr></table> <h4>Configuration options: </h4> These can reside either in the configuration file or be given as command line arguments. <br> <table width="600" border="0" cellspacing="0" cellpadding="1"><tr><td> <i>Name:</i></td><td><b>ipAddress</b>(-- ipAddress)</td></tr><tr><td><i>Arguments:</i></td><td>xxx.xxx.xxx.xxx</ td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> The IP address of this node as seen by the public Internet. You only need to override this if it cannot be autodetected, for example if you have a NAT (a.k.a. IP Masquerading) firewall/router, in which case you will need to set it to the IP address or DNS name of the internet-side interface of the router, which needs to be static (www.dyndns.org and similar services can help here if you have a dynamic IP). </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>listenPort</b>(- -listenPort)</td></tr><tr><td><i>Arguments:</i></td><td>{port no.}</td></tr><tr><td><i>Default val:</i></td><td>{random}</td></tr><tr><td><i>Description:</i></td><td> The port to listen for incoming FNP (Freenet Node <b style="color:black;background-color:#ffff66">Protocol</b>) connections on. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>clientPort</b>(- -clientPort)</td></tr><tr><td><i>Arguments:</i></td><td>{port no.}</td></tr><tr><td><i>Default val:</i></td><td>8481</td></tr><tr><td><i>Description:</i></td><td> The port to listen for local FCP (Freenet Client <b style="color:black;background-color:#ffff66">Protocol</b>) connections on. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>fcpHosts</b>(-- fcpHosts)</td></tr><tr><td><i>Arguments:</i></td><td>{host list}</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> A comma-separated list of hosts that may connect to the FCP port (clientPort).  If left blank, only the localhost will be allowed. If you set this, make sure localhost is included in the list or  access won't be allowed from the local machine. May be given as IP addresses or host names. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>adminPassword</b>(--adminPassword)</td></tr><tr><td><i>Arguments:</i></td><td>{string}</ td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> If this is set then users that can provide the password can can have administrative access. It is recommended that you do not use this without also using adminPeer below in which case both are required. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>adminPeer</b>(-- adminPeer)</td></tr><tr><td><i>Arguments:</i></td><td>{Identity FieldSet}</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> If this is set, then users that are authenticated owners of the given PK identity can have administrative access. If adminPassword is also set both are required. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>transient</b>(-- transient)</td></tr><tr><td><i>Arguments:</i></td><td>yes|no</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Transient nodes do not give out references to themselves, and should therefore not receive any requests.  Set this to yes if you cannot receive incoming connections, or cannot keep the computer continuously online. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>doAnnounce</b>(- -doAnnounce)</td></tr><tr><td><i>Arguments:</i></td><td>yes|no</td></tr> <tr><td><i>Default val:</i></td><td>true</td></tr><tr><td><i>Description:</i></td><td> If this is true, the node will automatically announce to all nodes in the {seedFile} file, as specified by {announcementDelay}, etc. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>seedFile</b>(-- seedFile)</td></tr><tr><td><i>Arguments:</i></td><td>{file}</td></tr><tr><td><i>Default val:</i></td><td>seednodes.ref</td></tr><tr><td><i>Description:</i></td> <td> A file containing one or more node references which will be incorporated into the node's routing table on startup.  A reference is only added if there is no previously existing reference to that node. When this node announces, it will announce to the nodes listed in this file. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>diagnosticsPath</b>(--diagnosticsPath)</td></tr><tr><td><i>Arguments:</i></td><td>{dir}</td></tr><tr><td><i>Default val:</i></td><td>stats</td></tr><tr><td><i>Description:</i></td><td> The directory in which to save diagnostics data.  Defaults to {storePath}/stats if left blank. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>storeType</b>(-- storeType)</td></tr><tr><td><i>Arguments:</i></td><td>{string}</td></tr> <tr><td><i>Default val:</i></td><td>freenet</td></tr><tr><td><i>Description:</i></td><td> Datastore implementation. Put "native" (without the quotes) if you want the new native filesystem datastore, which stores the files in a directory. Put "convert" to convert from an old monolithic store to a native store. Note that convert uses lots of disk space while doing the conversion (approximately twice the datastore size), and the resulting store may be (temporarily) slightly larger than the old one due to block size mismatch (this will be fixed as soon as the node tries to add a file to the store). </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>nodeFile</b>(-- nodeFile)</td></tr><tr><td><i>Arguments:</i></td><td>{file}</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> The path to the file containing the node's private key, DSA group, cipher key, etc.  Defaults to node_{port} in the current directory. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>storeFile</b>(-- storeFile)</td></tr><tr><td><i>Arguments:</i></td><td>{file}{,..}</td></ tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> The path to the single directory containing the data store.  The total maximum size of the files in the directory is given by {storeSize}. It will create new files in this dir, and DELETE OLD ONES. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>storeSize</b>(-- storeSize)</td></tr><tr><td><i>Arguments:</i></td><td>{bytes}</td></tr><tr><td><i>Default val:</i></td><td>268435456</td></tr><tr><td><i>Description:</i></td><td> The byte size of each data store file.  If there is more than one file, the total size of the store is the product of the number of files and {storeSize}. The maximum sized file that will be cached is 1/200th of this value, so we recommend the default 256MB, to cache the largest common file size on freenet, 1MB plus some headers </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>storeBlockSize</ b>(--storeBlockSize)</td></tr><tr><td><i>Arguments:</i></td><td>{bytes}</td></tr><tr><td><i>Default val:</i></td><td>4096</td></tr><tr><td><i>Description:</i></td><td> Size of blocks in the underlying filesystem for purposes of calculating space usage when storeType=native. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>storeCipherName</b>(--storeCipherName)</td></tr><tr><td><i>Arguments:</i></td><td>{ string}</td></tr><tr><td><i>Default val:</i></td><td>Twofish</td></tr><tr><td><i>Description:</i></td><td> The name of a symmetric cipher algorithm to encrypt the datastore contents with.  Supported algorithms are "Twofish", "Rijndael", and "null", "none", or "void" (for no encryption). </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>storeCipherWidth </b>(--storeCipherWidth)</td></tr><tr><td><i>Arguments:</i></td><td>{ integer}</td></tr><tr><td><i>Default val:</i></td><td>128</td></tr><tr><td><i>Description:</i></td><td> The width in bits of the cipher key to use for the datastore. The allowed values for this will depend on the cipher algorithm. Twofish allows 64, 128, 192, or 256, while Rijndael allows 128, 192, or 256. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>routingDir</b>(- -routingDir)</td></tr><tr><td><i>Arguments:</i></td><td>{directory}</td> </tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> The directory in which to store the routing table files. Defaults to parent dir of storeDir. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>useDSIndex</b>(- -useDSIndex)</td></tr><tr><td><i>Arguments:</i></td><td>true|false</td></tr><tr><td><i>Default val:</i></td><td>true</td></tr><tr><td><i>Description:</i></td><td> Use a datastore index file. Shorter startup time, but we have to run checkpoints, which lock the datastore, causing a hiccup </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>bandwidthLimit</ b>(--bandwidthLimit)</td></tr><tr><td><i>Arguments:</i></td><td>{bytes/ sec}</td></tr><tr><td><i>Default val:</i></td><td>100000</td></tr><tr><td><i>Description:</i></td><td> The maximum number of bytes per second to transmit, totaled between incoming and outgoing connections.  Ignored if either inputBandwidthLimit or outputBandwidthLimit is nonzero. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> inputBandwidthLimit</b>(--inputBandwidthLimit)</td></tr><tr><td><i> Arguments:</i></td><td>{bytes/sec}</td></tr><tr><td><i>Default val:</i></td><td>0</td></tr><tr><td><i>Description:</i></td><td> If nonzero, specifies an independent limit for incoming data only. (overrides bandwidthLimit if nonzero) </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> outputBandwidthLimit</b>(--outputBandwidthLimit)</td></tr><tr><td><i> Arguments:</i></td><td>{bytes/sec}</td></tr><tr><td><i>Default val:</i></td><td>0</td></tr><tr><td><i>Description:</i></td><td> If nonzero, specifies an independent limit for outgoing data only. (overrides bandwidthLimit if nonzero) </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> averageBandwidthLimit</b>(--averageBandwidthLimit)</td></tr><tr><td><i> Arguments:</i></td><td>{bytes/sec}</td></tr><tr><td><i>Default val:</i></td><td>0</td></tr><tr><td><i>Description:</i></td><td> The maximum number of bytes per second to transmit (averaged over a week), totaled between incoming and outgoing connections.  Error to define it if any of (average)inputBandwidthLimit or (average)outputBandwidthLimit is nonzero. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> averageInputBandwidthLimit</b>(--averageInputBandwidthLimit)</td></tr><tr><td><i>Arguments:</i></td><td>{bytes/sec}</td></tr><tr><td><i>Default val:</i></td><td>0</td></tr><tr><td><i>Description:</i></td><td> If nonzero, specifies an independent limit for incoming data only (averaged over a week). (overrides averageBandwidthLimit if nonzero) </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> averageOutputBandwidthLimit</b>(--averageOutputBandwidthLimit)</td></tr> <tr><td><i>Arguments:</i></td><td>{bytes/sec}</td></tr><tr><td><i> Default val:</i></td><td>0</td></tr><tr><td><i>Description:</i></td><td> If nonzero, specifies an independent limit for outgoing data only (averaged over a week). (overrides bandwidthLimit if nonzero) </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> maxNodeConnections</b>(--maxNodeConnections)</td></tr><tr><td><i> Arguments:</i></td><td>{int}</td></tr><tr><td><i>Default val:</i></td><td>60</td></tr><tr><td><i>Description:</i></td><td> The maximum number of incoming and outgoing connections to allow at the same time. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> maxConnectionsPerMinute</b>(--maxConnectionsPerMinute)</td></tr><tr><td> <i>Arguments:</i></td><td>{int}</td></tr><tr><td><i>Default val:</i></td><td>60</td></tr><tr><td><i>Description:</i></td><td> The maximum number of outgoing connections established in a one minute period. Deprecated and ignored. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> maxConnectionsMinute</b>(--maxConnectionsMinute)</td></tr><tr><td><i> Arguments:</i></td><td>{milliseconds}</td></tr><tr><td><i>Default val:</i></td><td>60000</td></tr><tr><td><i>Description:</i></td><td> The length of the period over which there must be at most maxConnectionsPerMinute connections. Deprecated and ignored. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> maxRequestsPerInterval</b>(--maxRequestsPerInterval)</td></tr><tr><td><i>Arguments:</i></td><td>{int}</td></tr><tr><td><i>Default val:</i></td><td>300</td></tr><tr><td><i>Description:</i></td><td> The maximum number of outgoing connections established per maxRequestsInterval. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> maxRequestsInterval</b>(--maxRequestsInterval)</td></tr><tr><td><i> Arguments:</i></td><td>{milliseconds}</td></tr><tr><td><i>Default val:</i></td><td>60000</td></tr><tr><td><i>Description:</i></td><td> The length of the period over which there must be at most maxRequestsPerInterval connections. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>logLevel</b>(-- logLevel)</td></tr><tr><td><i>Arguments:</i></td><td>{word}</td></tr><tr><td><i>Default val:</i></td><td>normal</td></tr><tr><td><i>Description:</i></td><td> The error reporting threshold, one of: Error:   Errors only Normal: Report significant events Minor:   Report minor events Debug:   Report events only of relevance when debugging </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>logFile</b>(-- logFile)</td></tr><tr><td><i>Arguments:</i></td><td>{filename}|NO</td></ tr><tr><td><i>Default val:</i></td><td>freenet.log</td></tr><tr><td><i>Description:</i></td><td> The name of the log file (`NO' to log to standard out) </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>logFormat</b>(-- logFormat)</td></tr><tr><td><i>Arguments:</i></td><td>{tmpl.}</td></tr><tr><td><i>Default val:</i></td><td>d (c, t): m</td></tr><tr><td><i>Description:</i></td><td> A template string for log messages.  All non-alphabet characters are reproduced verbatim. Alphabet characters are substituted as follows: d = date (timestamp), c = class name of the source object, h = hashcode of the object, t = thread name, p = priority, m = the actual log message </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>logDate</b>(-- logDate)</td></tr><tr><td><i>Arguments:</i></td><td>{tmpl.}</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> A template for formatting the timestamp in log messages.  Defaults to the locale specific fully specified date format.  The template string is an ordinary Java date/time template - see: http://java.sun.com/products/jdk/1.4/docs/api/java.text.SimpleDateFormat .html </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>rtMaxRefs</b>(-- rtMaxRefs)</td></tr><tr><td><i>Arguments:</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>50</td></tr><tr><td><i>Description:</i></td><td> The number of references allowed per node in the routing table. This should not be set too high. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>rtMaxNodes</b>(- -rtMaxNodes)</td></tr><tr><td><i>Arguments:</i></td><td>{integer}</td></ tr><tr><td><i>Default val:</i></td><td>50</td></tr><tr><td><i>Description:</i></td><td> The number of unique nodes that can be contained in the routing table. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>maxRoutingSteps</b>(--maxRoutingSteps)</td></tr><tr><td><i>Arguments:</i></td><td>{ integer}</td></tr><tr><td><i>Default val:</i></td><td>40</td></tr><tr><td><i>Description:</i></td><td> The maximum number or node refs that will be used to route a request before RNFing. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>messageStoreSize </b>(--messageStoreSize)</td></tr><tr><td><i>Arguments:</i></td><td>{ integer}</td></tr><tr><td><i>Default val:</i></td><td>1000</td></tr><tr><td><i>Description:</i></td><td> The number of outstanding message replies the node will wait for before it starts to abandon them. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>failureTableSize </b>(--failureTableSize)</td></tr><tr><td><i>Arguments:</i></td><td>{ integer}</td></tr><tr><td><i>Default val:</i></td><td>1000</td></tr><tr><td><i>Description:</i></td><td> The number keys that failed to be retrieved the node should key track of. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>failureTableTime </b>(--failureTableTime)</td></tr><tr><td><i>Arguments:</i></td><td>{ milliseconds}</td></tr><tr><td><i>Default val:</i></td><td>1800000</td></tr><tr><td><i>Description:</i></td><td> The amount of time to keep keys cache keys that could not be found and automatically fail requests for them. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>minCP</b>(-- minCP)</td></tr><tr><td><i>Arguments:</i></td><td>{number between 0 and 1}</td></tr><tr><td><i>Default val:</i></td><td>0.01</td></tr><tr><td><i>Description:</i></td><td> Lower bound on Contact Probability of nodes in the Routing Table. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> failuresLookupARK</b>(--failuresLookupARK)</td></tr><tr><td><i>Arguments :</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>20</td></tr><tr><td><i>Description:</i></td><td> Number of consecutive failures required to trigger an ARK lookup. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>minARKDelay</b>( --minARKDelay)</td></tr><tr><td><i>Arguments:</i></td><td>{milliseconds} </td></tr><tr><td><i>Default val:</i></td><td>900000</td></tr><tr><td><i>Description:</i></td><td> Minimum time that a node in the routing table must have been uncontactable for before we can trigger an ARK lookup. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> routeConnectTimeout</b>(--routeConnectTimeout)</td></tr><tr><td><i> Arguments:</i></td><td>{millis}</td></tr><tr><td><i>Default val:</i></td><td>10000</td></tr><tr><td><i>Description:</i></td><td> The time to wait for connections to be established and authenticated before passing by a node while routing out. Connections that are by passed are still finished and cached for the time set by {connectionTimeout} (in milliseconds). </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>maxHopsToLive</b>(--maxHopsToLive)</td></tr><tr><td><i>Arguments:</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>25</td></tr><tr><td><i>Description:</i></td><td> When forwarding a request, the node will reduce the HTL to this value if it is found to be in excess. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>announcementHTL</b>(--announcementHTL)</td></tr><tr><td><i>Arguments:</i></td><td>{ integer}</td></tr><tr><td><i>Default val:</i></td><td>15</td></tr><tr><td><i>Description:</i></td><td> The number of nodes that each announcement message should besent to. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> announcementAttempts</b>(--announcementAttempts)</td></tr><tr><td><i> Arguments:</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>3</td></tr><tr><td><i>Description:</i></td><td> The number of attempts to make at announcing this node per initial peer. Zero means the node will not announce itself. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> announcementPollInterval</b>(--announcementPollInterval)</td></tr><tr><td><i>Arguments:</i></td><td>{milliseconds}</td></tr><tr><td><i>Default val:</i></td><td>900000</td></tr><tr><td><i>Description:</i></td><td> The time between polling for 1 hours no incoming requests to force reannouncement. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> announcementThreads</b>(--announcementThreads)</td></tr><tr><td><i> Arguments:</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>3</td></tr><tr><td><i>Description:</i></td><td> If we run out of seed nodes, we can use other nodes from therouting table to announce to. However, since the trust levelof these nodes is unknown, this is not recommended for thetruly paranoid. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> announcementUseRT</b>(--announcementUseRT)</td></tr><tr><td><i>Arguments :</i></td><td>yes|no</td></tr><tr><td><i>Default val:</i></td><td>true</td></tr><tr><td><i>Description:</i></td><td> announce to nodes from routing table?. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>initialRequests</b>(--initialRequests)</td></tr><tr><td><i>Arguments:</i></td><td>{ integer}</td></tr><tr><td><i>Default val:</i></td><td>10</td></tr><tr><td><i>Description:</i></td><td> The number of keys to request from the returned close values after an Announcement (this is per announcement made). </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> initialRequestHTL</b>(--initialRequestHTL)</td></tr><tr><td><i>Arguments :</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>15</td></tr><tr><td><i>Description:</i></td><td> The hops that initial requests should make. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>doLoadBalance</b>(--doLoadBalance)</td></tr><tr><td><i>Arguments:</i></td><td>yes|no</td></tr><tr><td><i>Default val:</i></td><td>true</td></tr><tr><td><i>Description:</i></td><td> Whether to emply load balancing algorithms against the network. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>localIsOK</b>(-- localIsOK)</td></tr><tr><td><i>Arguments:</i></td><td>yes|no</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> set yes to allow permanent nodes with non-internet-resolvable addresses. Do not use this except in a local testing network. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>dontLimitClients </b>(--dontLimitClients)</td></tr><tr><td><i>Arguments:</i></td><td>yes| no</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> set yes to not bandwidth throttle connections to LocalInterfaces<a href='tiki-editpage.php?page=LocalInterfaces' class='wiki'>?</a> i.e. FCP and mainport. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> mainportURIOverride</b>(--mainportURIOverride)</td></tr><tr><td><i> Arguments:</i></td><td>URI</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> URI to mainport servlet, e.g. for SSL tunneling. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> distributionURIOverride</b>(--distributionURIOverride)</td></tr><tr><td> <i>Arguments:</i></td><td>URI</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> URI to distribution servlet, e.g. for SSL tunneling. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>aggressiveGC</b> (--aggressiveGC)</td></tr><tr><td><i>Arguments:</i></td><td>{seconds}</ td></tr><tr><td><i>Default val:</i></td><td>0</td></tr><tr><td><i>Description:</i></td><td> How often to do aggressive garbage collection. May impact performance but should reduce working set.  Set to 0 to disable. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> configUpdateInterval</b>(--configUpdateInterval)</td></tr><tr><td><i> Arguments:</i></td><td>{minutes}</td></tr><tr><td><i>Default val:</i></td><td>5</td></tr><tr><td><i>Description:</i></td><td> How often to check for config file changes.  Set to 0 to disable. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>services</b>(-- services)</td></tr><tr><td><i>Arguments:</i></td><td>service_0,service_1 ,...</td></tr><tr><td><i>Default val:</i></td><td>mainport, distribution</td></tr><tr><td><i>Description:</i></td><td> A comma delimited list of services that are run when the node starts. If you don't know what this means, just accept the defaults. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>distribution. class</b>(--distribution.class)</td></tr><tr><td><i>Arguments:</i></td><td>{class name}</td></tr><tr><td><i>Default val:</i></td><td>freenet.node.http.DistributionServlet</td></tr><tr><td> <i>Description:</i></td><td> The Java class of the distribution servlet. You shouldn't need to touch this. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>distribution. port</b>(--distribution.port)</td></tr><tr><td><i>Arguments:</i></td><td>{port number}</td></tr><tr><td><i>Default val:</i></td><td>8891</td></tr><tr><td><i>Description:</i></td><td> The port that the distribution servlet listens for HTTP requests on. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>distribution. params.unpacked</b>(--distribution.params.unpacked)</td></tr><tr><td><i> Arguments:</i></td><td>{directory}</td></tr><tr><td><i>Default val:</i></td><td>.</td></tr><tr><td><i>Description:</i></td><td> A directory containing (some of) the files needed for the Distribution Servlet - for example, a CVS tree, or where the UNIX tarball was unpacked. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>distribution. allowedHosts</b>(--distribution.allowedHosts)</td></tr><tr><td><i> Arguments:</i></td><td>{list of IP addresses}</td></tr><tr><td><i>Default val:</i></td><td>*</td></tr><tr><td><i>Description:</i></td><td> These IP addresses will be allowed to access the distribution pages generated by the DistributionServlet. Default * means everyone. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>distribution. params.distribDir</b>(--distribution.params.distribDir)</td></tr><tr><td><i>Arguments:</i></td><td>{directory}</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> Directory used by the node to store redistributibles for the Distribution Servlet - there is rarely any need to override this. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>authTimeout</b>( --authTimeout)</td></tr><tr><td><i>Arguments:</i></td><td>{millis}</td></tr><tr><td><i>Default val:</i></td><td>30000</td></tr><tr><td><i>Description:</i></td><td> How long to wait for authentication before giving up (in milliseconds) </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> connectionTimeout</b>(--connectionTimeout)</td></tr><tr><td><i>Arguments :</i></td><td>{millis}</td></tr><tr><td><i>Default val:</i></td><td>600000</td></tr><tr><td><i>Description:</i></td><td> How long to listen on an inactive connection before closing (if reply address is known) </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>hopTimeExpected</b>(--hopTimeExpected)</td></tr><tr><td><i>Arguments:</i></td><td>{ millis}</td></tr><tr><td><i>Default val:</i></td><td>4000</td></tr><tr><td><i>Description:</i></td><td> The expected time it takes a Freenet node to pass a message. Used to calculate timeout values for requests. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>hopTimeDeviation </b>(--hopTimeDeviation)</td></tr><tr><td><i>Arguments:</i></td><td>{ millis}</td></tr><tr><td><i>Default val:</i></td><td>7000</td></tr><tr><td><i>Description:</i></td><td> The expected standard deviation in hopTimeExpected. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>maximumThreads</ b>(--maximumThreads)</td></tr><tr><td><i>Arguments:</i></td><td>{integer }</td></tr><tr><td><i>Default val:</i></td><td>120</td></tr><tr><td><i>Description:</i></td><td> Should we use thread management?  If this number is defined and non-zero, this specifies the max number of threads in the pool.  If this is overrun connections will be rejected and events won't execute on time. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> doRequestTriageByDelay</b>(--doRequestTriageByDelay)</td></tr><tr><td><i>Arguments:</i></td><td>true/false</td></tr><tr><td><i>Default val:</i></td><td>true</td></tr><tr><td><i>Description:</i></td><td> If true, above 3000ms ticker delay requests will be rejected, above 1000ms, requests except those in the datastore will be rejected, and above 500ms, requests except those in the most successful keyspace segment will be rejected. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>overloadLow</b>( --overloadLow)</td></tr><tr><td><i>Arguments:</i></td><td>{float between 0 and 1}</td></tr><tr><td><i>Default val:</i></td><td>0.85</td></tr><tr><td><i>Description:</i></td><td> The node will start to selectively reject requests above this load level. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>overloadHigh</b> (--overloadHigh)</td></tr><tr><td><i>Arguments:</i></td><td>{float between 0 and 1}</td></tr><tr><td><i>Default val:</i></td><td>0.9</td></tr><tr><td><i>Description:</i></td><td> The node will reject all QueryRequests<a href='tiki-editpage.php?page=QueryRequests' class='wiki'>?</a> above this load level. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> requestDelayCutoff</b>(--requestDelayCutoff)</td></tr><tr><td><i> Arguments:</i></td><td>{milliseconds}</td></tr><tr><td><i>Default val:</i></td><td>1000</td></tr><tr><td><i>Description:</i></td><td> The node will reject nearly all incoming queries when routingTime is over this value. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> successfulDelayCutoff</b>(--successfulDelayCutoff)</td></tr><tr><td><i> Arguments:</i></td><td>{milliseconds}</td></tr><tr><td><i>Default val:</i></td><td>3000</td></tr><tr><td><i>Description:</i></td><td> The node will reject ALL incoming queries above this routingTime. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>blockSize</b>(-- blockSize)</td></tr><tr><td><i>Arguments:</i></td><td>{bytes}</td></tr><tr><td><i>Default val:</i></td><td>4096</td></tr><tr><td><i>Description:</i></td><td> What size should the blocks have when moving data? </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>streamBufferSize </b>(--streamBufferSize)</td></tr><tr><td><i>Arguments:</i></td><td>{ bytes}</td></tr><tr><td><i>Default val:</i></td><td>16384</td></tr><tr><td><i>Description:</i></td><td> The default size of stream buffers. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>maximumPadding</ b>(--maximumPadding)</td></tr><tr><td><i>Arguments:</i></td><td>{bytes}</td></tr><tr><td><i>Default val:</i></td><td>65536</td></tr><tr><td><i>Description:</i></td><td> The maximum number of bytes of padding to allow between messages and in Void messages. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> logInboundContacts</b>(--logInboundContacts)</td></tr><tr><td><i> Arguments:</i></td><td>true/false</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Set true to enable inbound contact monitoring. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> logOutboundContacts</b>(--logOutboundContacts)</td></tr><tr><td><i> Arguments:</i></td><td>true/false</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Set true to enable outbound contact monitoring. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> logInboundRequests</b>(--logInboundRequests)</td></tr><tr><td><i> Arguments:</i></td><td>true/false</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Set true to enable per host inbound request monitoring. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> logOutboundRequests</b>(--logOutboundRequests)</td></tr><tr><td><i> Arguments:</i></td><td>true/false</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Set true to enable per host outbound request monitoring. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>logOutputBytes</ b>(--logOutputBytes)</td></tr><tr><td><i>Arguments:</i></td><td>true/ false</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Set true to.count TCP bytes sent for diagnostics. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>watchme</b>(-- watchme)</td></tr><tr><td><i>Arguments:</i></td><td>true/false</td></tr> <tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Debugging only, setting this to true will remove your anonymity!. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> logInboundInsertRequestDist</b>(--logInboundInsertRequestDist)</td></tr> <tr><td><i>Arguments:</i></td><td>true/false</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Set true to enable logging of inbound InsertRequest<a href='tiki-editpage.php?page=InsertRequest' class='wiki'>?</a> key distribution. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>watchmeRetries</ b>(--watchmeRetries)</td></tr><tr><td><i>Arguments:</i></td><td>{integer }</td></tr><tr><td><i>Default val:</i></td><td>3</td></tr><tr><td><i>Description:</i></td><td> Number of times watchMe will attempt to initialize. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> logSuccessfulInsertRequestDist</b>(--logSuccessfulInsertRequestDist)</td></tr><tr><td><i>Arguments:</i></td><td>true/false</td></tr><tr><td><i> Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Set true to enable logging of successful inbound InsertRequests' key distribution. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> defaultResetProbability</b>(--defaultResetProbability)</td></tr><tr><td> <i>Arguments:</i></td><td>{probability}</td></tr><tr><td><i>Default val:</i></td><td>0.05</td></tr><tr><td><i>Description:</i></td><td> The node will have this probability, on average (it varies according to load unless you set doLoadBalance=no), of resetting the datasource. Increase this to get more load, reduce it to get less load. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>FECTempDir</b>(- -FECTempDir)</td></tr><tr><td><i>Arguments:</i></td><td>{directory}</td> </tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> Dir. used for FEC temp files. You don't need to set this. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> FECInstanceCacheSize</b>(--FECInstanceCacheSize)</td></tr><tr><td><i> Arguments:</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>1</td></tr><tr><td><i>Description:</i></td><td> Number of FEC instances to cache. Set to 1 unless you expect more than one simultaneous FEC operation. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> FECMaxConcurrentCodecs</b>(--FECMaxConcurrentCodecs)</td></tr><tr><td><i>Arguments:</i></td><td>{integer}</td></tr><tr><td><i>Default val:</i></td><td>1</td></tr><tr><td><i>Description:</i></td><td> Number of concurrent FEC encodes/decodes allowed. Each codec can use up to 24Mb of memory. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>FEC.Encoders.0. class</b>(--FEC.Encoders.0.class)</td></tr><tr><td><i>Arguments:</i></td><td>{class name}</td></tr><tr><td><i>Default val:</i></td><td>OnionFECEncoder</td></tr><tr><td><i>Description:</i></ td><td> Default FEC encoder implementation. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>FEC.Decoders.0. class</b>(--FEC.Decoders.0.class)</td></tr><tr><td><i>Arguments:</i></td><td>{class name}</td></tr><tr><td><i>Default val:</i></td><td>OnionFECDecoder</td></tr><tr><td><i>Description:</i></ td><td> Default FEC decoder implementation. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>tempDir</b>(-- tempDir)</td></tr><tr><td><i>Arguments:</i></td><td>{directory}</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> The directory used for temporary files. Used currently by fproxy and the FCP FEC mechanism, if their individual temp dirs are not set. If this is left unset, it will create a tempdir in the datastore (if the datastore is native). </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>publicNode</b>(- -publicNode)</td></tr><tr><td><i>Arguments:</i></td><td>true/false</td></tr><tr><td><i>Default val:</i></td><td>false</td></tr><tr><td><i>Description:</i></td><td> Disables anonymity threatening servlets and infolets on a multi-user machine. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b> filterPassThroughMimeTypes</b>(--filterPassThroughMimeTypes)</td></tr><tr><td><i>Arguments:</i></td><td>comma delimited list of MIME types</td></tr><tr><td><i>Default val:</i></td><td>text/plain,image/jpeg,image/gif,image/png</td></tr><tr> <td><i>Description:</i></td><td> safe MIME types that will be passed through to the browser without query or filtering. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport.class</ b>(--mainport.class)</td></tr><tr><td><i>Arguments:</i></td><td> interface class</td></tr><tr><td><i>Default val:</i></td><td>freenet.interfaces.servlet.MultipleHttpServletContainer </td></tr><tr><td><i>Description:</i></td><td> Name of the interface class to run the mainport service. You do not need to change this. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport.port</b>(--mainport.port)</td></tr><tr><td><i>Arguments:</i></td><td>port number</td></tr><tr><td><i>Default val:</i></td><td>8888</td></tr><tr><td><i>Description:</i></td><td> Port to run the main Freenet HTTP interface on... this is the port that is accessed by your web browser when you are browsing freenet via fproxy, or looking at the various status monitors. This is normally only accessible from localhost, and is different from the public FNP port that other freenet nodes talk to, the FCP port that client programs talk to, and the distribution port that you can run a freenet distribution website on. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport. allowedHosts</b>(--mainport.allowedHosts)</td></tr><tr><td><i>Arguments: </i></td><td>Comma delimited list of IP addresses, netmasks or hostnames</td></tr><tr><td><i>Default val:</i></td><td>127.0.0.0/8</td></tr><tr><td><i>Description:</i></td><td> List of IP addresses (for example "192.168.1.7"), DNS names ("erica" or "www.nsa.gov") or netmasks ("192.168.1.0/24") of hosts (computers) that should be allowed to access the main web interface of your freenet node. Defaults to localhost (127.0.0.0/8) only. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport. bindAddress</b>(--mainport.bindAddress)</td></tr><tr><td><i>Arguments:</ i></td><td>IP address or "*"</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> IP address of one interface for the main freenet web interface to listen on, or "*" to listen on all interfaces. Will be automatically determined from mainport.allowedHosts if not given<dl><dt> leave it alone. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name</dt><dd></i></td><td><b>mainport.params. servlet.1.uri</b>(--mainport.params.servlet.1.uri)</td></tr><tr><td><i> Arguments:</i></td><td>path</td></tr><tr><td><i>Default val:</i></td><td>/</td></tr><tr><td><i>Description:</i></td><td> Path within mainport for fproxy. Leave this alone. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport.params. servlet.1.method</b>(--mainport.params.servlet.1.method)</td></tr><tr><td><i>Arguments:</i></td><td>HTTP method</td></tr><tr><td><i>Default val:</i></td><td>GET</td></tr><tr><td><i>Description:</i></td><td> HTTP method for fproxy. Leave this alone. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport.params. servlet.1.class</b>(--mainport.params.servlet.1.class)</td></tr><tr><td> <i>Arguments:</i></td><td>servlet class</td></tr><tr><td><i>Default val:</i></td><td>freenet.client.http.FproxyServlet</td></tr><tr><td><i> Description:</i></td><td> servlet class to run fproxy. Leave this alone. </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport.params. servlet.1.name</b>(--mainport.params.servlet.1.name)</td></tr><tr><td><i>Arguments:</i></td><td>string</td></tr><tr><td><i>Default val:</i></td><td>Freenet HTTP proxy (fproxy)</td></tr><tr><td><i>Description:</i></td><td> name of first servlet on mainport (normally fproxy - "Freenet HTTP proxy (fproxy)"). Leave this alone.). </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport.params. servlet.1.params.requestHtl</b>(--mainport.params.servlet.1.params. requestHtl)</td></tr><tr><td><i>Arguments:</i></td><td>integer HTL value between 0 and maxHopsToLive</td></tr><tr><td><i>Default val:</i></td><td>15</td></tr><tr><td><i>Description:</i></td><td> hops to live (HTL) of requests made by fproxy </td></tr><tr><td colspan=2><hr></td></tr><tr><td><i>Name:</i></td><td><b>mainport.params. servlet.1.params.passThroughMimeTypes</b>(--mainport.params.servlet.1. params.passThroughMimeTypes)</td></tr><tr><td><i>Arguments:</i></td><td> comma delimited list of MIME types</td></tr><tr><td><i>Default val:</i></td><td></td></tr><tr><td><i>Description:</i></td><td> MIME types regarded as safe that are passed to the browser without filtering or warning in fproxy. The default is empty (""), which means to use the node global default filterPassThroughMimeTypes </td></tr>&