[tor-commits] [onionoo/master] Remove old URLs from protocol specification.

[karsten at torproject.org]

commit 52c1cb4ba23c46cc70feae06961abd9f152a9fc8
Author: Karsten Loesing <karsten.loesing at gmx.net>
Date:   Sun Aug 26 17:37:46 2012 +0200

    Remove old URLs from protocol specification.
---
 web/index.html |  211 --------------------------------------------------------
 1 files changed, 0 insertions(+), 211 deletions(-)

diff --git a/web/index.html b/web/index.html
index aba746d..2ed5075 100755
--- a/web/index.html
+++ b/web/index.html
@@ -87,76 +87,6 @@ running in the last bridge network status.
 Required field.</li>
 </ul>
 </ul>
-<p>The following methods are available that all return a single summary
-document.
-The method and its parameters determines which relay and/or bridge
-summaries are included in the response.
-<font color="red">These methods have been deprecated on May 14, 2012 and
-have been removed on July 17, 2012.
-See the Methods section at the end of this page.</font>
-</p>
-<table border="0" cellpadding="4" cellspacing="0" summary="">
-<colgroup>
-<col width="350">
-<col width="650">
-</colgroup>
-<tr>
-<td><b>GET summary/all</b></td>
-<td>Return summaries of all relays and bridges that are currently running
-or that have been running in the past week.
-<font color="red">New method:
-<b>GET summary</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET summary/running</b></td>
-<td>Return summaries of all relays and bridges that are currently
-running.
-<font color="red">New method:
-<b>GET summary?running=true</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET summary/relays</b></td>
-<td>Return summaries of all relays that are currently running or that have
-been running in the past week, but don't include any bridges.
-<font color="red">New method:
-<b>GET summary?type=relay</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET summary/bridges</b></td>
-<td>Return summaries of all bridges that are currently running or that
-have been running in the past week, but don't include any relays.
-<font color="red">New method:
-<b>GET summary?type=bridge</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET summary/search/<i>:searchtext</i></b></td>
-<td>Return summaries of all relays and bridges with <i>:searchtext</i>
-matching the beginning of a nickname, (possibly $-prefixed) fingerprint,
-IP address, or (possibly $-prefixed) hashed fingerprint.
-Searches are case-insensitive.
-Full fingerprints should always be hashed using SHA-1, regardless of
-searching for a relay or a bridge, in order to not accidentally leak
-non-hashed bridge fingerprints in the URL.
-<font color="red">New method:
-<b>GET summary?search=:searchtext</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET summary/lookup/<i>:fingerprint</i></b></td>
-<td>Return the summary of the relay or bridge with <i>:fingerprint</i>
-matching the fingerprint or hashed fingerprint.
-Fingerprints should always be hashed using SHA-1, regardless of looking up
-a relay or a bridge, in order to not accidentally leak non-hashed bridge
-fingerprints in the URL.
-<font color="red">New method:
-<b>GET summary?lookup=:fingerprint</b></font>
-</td>
-</tr>
-</table>
 <br>
 <a name="details"></a>
 <h3><a href="#details" class="anchor">Detail documents</a></h3>
@@ -402,76 +332,6 @@ Optional field.</li>
 </ul>
 </li>
 </ul>
-<p>The following methods are available that all return a single details
-document.
-The method and its parameters determines which relay and/or bridge
-details are included in the response.
-<font color="red">These methods have been deprecated on May 14, 2012 and
-have been removed on July 17, 2012.
-See the Methods section at the end of this page.</font>
-</p>
-<table border="0" cellpadding="4" cellspacing="0" summary="">
-<colgroup>
-<col width="350">
-<col width="650">
-</colgroup>
-<tr>
-<td><b>GET details/all</b></td>
-<td>Return details of all relays and bridges that are currently running
-or that have been running in the past week.
-<font color="red">New method:
-<b>GET details</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET details/running</b></td>
-<td>Return details of all relays and bridges that are currently
-running.
-<font color="red">New method:
-<b>GET details?running=true</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET details/relays</b></td>
-<td>Return details of all relays that are currently running or that have
-been running in the past week, but don't include any bridges.
-<font color="red">New method:
-<b>GET details?type=relay</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET details/bridges</b></td>
-<td>Return details of all bridges that are currently running or that have
-been running in the past week, but don't include any relays.
-<font color="red">New method:
-<b>GET details?type=bridge</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET details/search/<i>:searchtext</i></b></td>
-<td>Return details of all relays and bridges with <i>:searchtext</i>
-matching the beginning of a nickname, (possibly $-prefixed) fingerprint,
-IP address, or (possibly $-prefixed) hashed fingerprint.
-Searches are case-insensitive.
-Full fingerprints should always be hashed using SHA-1, regardless of
-searching for a relay or a bridge, in order to not accidentally leak
-non-hashed bridge fingerprints in the URL.
-<font color="red">New method:
-<b>GET details?search=:searchtext</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET details/lookup/<i>:fingerprint</i></b></td>
-<td>Return the details of the relay or bridge with <i>:fingerprint</i>
-matching the fingerprint or hashed fingerprint.
-Fingerprints should always be hashed using SHA-1, regardless of looking up
-a relay or a bridge, in order to not accidentally leak non-hashed bridge
-fingerprints in the URL.
-<font color="red">New method:
-<b>GET details?lookup=:fingerprint</b></font>
-</td>
-</tr>
-</table>
 <br>
 <a name="bandwidth"></a>
 <h3><a href="#bandwidth" class="anchor">Bandwidth documents</a></h3>
@@ -566,77 +426,6 @@ The specification of bandwidth history objects is similar to those in the
 </ul>
 </li>
 </ul>
-<p>The following methods are available that all return a single document.
-The method and its parameters determines which relay and/or bridge
-bandwidth documents are included in the response.
-<font color="red">These methods have been deprecated on May 14, 2012 and
-have been removed on July 17, 2012.
-See the Methods section at the end of this page.</font>
-</p>
-<table border="0" cellpadding="4" cellspacing="0" summary="">
-<colgroup>
-<col width="350">
-<col width="650">
-</colgroup>
-<tr>
-<td><b>GET bandwidth/all</b></td>
-<td>Return bandwidth documents of all relays and bridges that are
-currently running or that have been running in the past week.
-<font color="red">New method:
-<b>GET bandwidth</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET bandwidth/running</b></td>
-<td>Return bandwidth documents of all relays and bridges that are
-currently running.
-<font color="red">New method:
-<b>GET bandwidth?running=true</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET bandwidth/relays</b></td>
-<td>Return bandwidth documents of all relays that are currently running or
-that have been running in the past week, but don't include any bridges.
-<font color="red">New method:
-<b>GET bandwidth?type=relay</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET bandwidth/bridges</b></td>
-<td>Return bandwidth documents of all bridges that are currently running
-or that have been running in the past week, but don't include any
-relays.
-<font color="red">New method:
-<b>GET bandwidth?type=bridge</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET details/search/<i>:searchtext</i></b></td>
-<td>Return bandwidth documents of all relays and bridges with
-<i>:searchtext</i> matching the beginning of a nickname, (possibly
-$-prefixed) fingerprint, IP address, or (possibly $-prefixed) hashed
-fingerprint.
-Searches are case-insensitive.
-Full fingerprints should always be hashed using SHA-1, regardless of
-searching for a relay or a bridge, in order to not accidentally leak
-non-hashed bridge fingerprints in the URL.
-<font color="red">New method:
-<b>GET bandwidth?search=:searchtext</b></font>
-</td>
-</tr>
-<tr>
-<td><b>GET bandwidth/lookup/<i>:fingerprint</i></b></td>
-<td>Return the bandwidth document of the relay or bridge with
-<i>:fingerprint</i> matching the fingerprint or hashed fingerprint.
-Fingerprints should always be hashed using SHA-1, regardless of looking up
-a relay or a bridge, in order to not accidentally leak non-hashed bridge
-fingerprints in the URL.
-<font color="red">New method:
-<b>GET bandwidth?lookup=:fingerprint</b></font>
-</td>
-</tr>
-</table>
 <br>
 <a name="weights"></a>
 <h3><a href="#weights" class="anchor">Weights documents</a></h3>