[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] r26662 - libmicrohttpd-docs/WWW
|
From: |
gnunet |
|
Subject: |
[GNUnet-SVN] r26662 - libmicrohttpd-docs/WWW |
|
Date: |
Fri, 29 Mar 2013 18:04:29 +0100 |
Author: grothoff
Date: 2013-03-29 18:04:29 +0100 (Fri, 29 Mar 2013)
New Revision: 26662
Modified:
libmicrohttpd-docs/WWW/index.html
Log:
-updating to GNU template
Modified: libmicrohttpd-docs/WWW/index.html
===================================================================
--- libmicrohttpd-docs/WWW/index.html 2013-03-29 16:23:40 UTC (rev 26661)
+++ libmicrohttpd-docs/WWW/index.html 2013-03-29 17:04:29 UTC (rev 26662)
@@ -1,28 +1,58 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
-<html><head>
-<meta http-equiv="Content-Type" content="text/html;charset=utf-8" >
-<title>GNU libmicrohttpd: a library for creating an embedded HTTP
server</title>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.69 -->
+
+<!-- Instructions for adapting this boilerplate to a new project: -->
+
+<!-- 1. In the line above starting "Parent-Version:", remove the
+ "$Revision...$" from around the revision number,
+ leaving just Parent-Version: and the number. -->
+
+<!-- 2. Replace "baz" with the name of your project.
+ You should be able to do this with search and replace;
+ making sure that the search is case insensitive and
+ that the case of the replacement matches the case
+ of the string found. In Emacs, query-replace will do this
+ when case-fold-search and case-replace are both non-nil
+ and both search and replacement string are given in lower case. -->
+
+<!-- 3. Of course update the actual information according to your project,
+ such as mailing lists, project locations, and maintainer name. -->
+
+<!-- 4. You can use the patch-from-parent script to semi-automate
+ merging future changes to the boilerplate with your file:
+
http://web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/patch-from-parent?root=www&content-type=text%2Fplain
+ -->
+
+<!-- If you would like to make sure your page validates with HTML5, that
+ would be a good thing. To do that, change the first line from
+ to /server/html5-header.html before trying the validation. Maybe
+ someday we will be able to make /server/header be HTML5. -->
+
+<title>Libmicrohttpd
+- GNU Project - Free Software Foundation</title>
<meta name="content-language" content="en">
+<meta name="description" content="a library for creating an embedded HTTP
server">
<meta name="language" content="en">
<meta name="author" content="Christian Grothoff">
<meta name="keywords"
content="libmicrohttpd,http,daemon,server,library,C,LGPL,eCos,free,Linux,GNU,GPL,SSL,TLS,digest,authentication,SHOUTcast">
<meta name="robots" content="index,follow">
<meta name="revisit-after" content="28 days">
<meta name="publisher" content="Christian Grothoff">
-<meta name="date" content="2011-12-1">
-<meta name="rights" content="(C) 2007, 2008, 2009, 2010, 2011 by Christian
Grothoff>";
+<meta name="date" content="2013-03-15">
+<meta name="rights" content="(C) 2007-2013 by Christian Grothoff>";
<meta http-equiv="expires" content="43200">
-</head>
-<body>
-<h1>GNU libmicrohttpd</h1>
-<a name="about"></a>
-<h2>About</h2>
-<p >
+
+<!--#include virtual="/server/banner.html" -->
+<!--#set var="article_name" value="/server/standards/boilerplate" -->
+<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+<h2>GNU Libmicrohttpd</h2>
+
+<p>
GNU libmicrohttpd is a small C library that is supposed to make it
easy to run an HTTP server as part of another application. GNU
-libmicrohttpd is free software and part of the <a
+GNU Libmicrohttpd is free software and part of the <a
href="http://gnu.org/";>GNU project</a>. Key features that distinguish
-libmicrohttpd from other projects are:
+GNU Libmicrohttpd from other projects are:
<ul>
<li>C library: fast and small</li>
<li>API is simple, expressive and fully reentrant</li>
@@ -37,79 +67,177 @@
<li>Support for SSL3 and TLS (requires libgcrypt and libgnutls, optional)</li>
<li>Binary is only about 32k (without TLS/SSL support and other optional
features)</li>
</ul>
-libmicrohttpd was started because the author needed an easy way to add
+GNU Libmicrohttpd was started because the author needed an easy way to add
a concurrent HTTP server to other projects. Existing alternatives
were either non-free, not reentrant, standalone, of terrible code
-quality or a combination thereof. Do not use libmicrohttpd if you are
+quality or a combination thereof. Do not use GNU Libmicrohttpd if you are
looking for a standalone HTTP server, there are many other projects
out there that provide that kind of functionality already. However,
if you want to be able to serve simple WWW pages from within your C or
C++ application, check it out.
</p>
-<p >
-libmicrohttpd is licensed under the
-<a href="http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html";>GNU
-LGPL v2.1</a> or at your
-option <a href="http://www.gnu.org/licenses/lgpl.html";>any later
-version</a>. If you disable HTTPS/SSL support, you can also choose
-the second license,
-the <a href="http://ecos.sourceware.org/license-overview.html";>eCos
-License</a>. If you have questions about licensing, please contact
-the
-<a href="http://grothoff.org/christian/";>maintainer</a>.
+<p>
+GNU libmicrohttpd is a <a href="http://www.gnu.org/";>GNU</a> package.
+Our official GNU website can be found
+at <a
href="http://www.gnu.org/software/libmicrohttpd/";>http://www.gnu.org/software/libmicrohttpd/</a>.
</p>
-<a name="download"></a>
-<h2>Download</h2>
-<p >
-You can find the current release including binaries for Windows
-<a href="ftp://ftp.gnu.org/gnu/libmicrohttpd/";>here</a> and on
-<a href="http://ftpmirror.gnu.org/libmicrohttpd/";>GNU ftp mirrors</a>.
-The latest version of the source code can be browsed from
-<a href="https://gnunet.org/svn/libmicrohttpd/";>here</a> or obtained using
-<pre>$ svn checkout https://gnunet.org/svn/libmicrohttpd/</pre>
+
+
+<h3 id="download">Downloading
+ Libmicrohttpd</h3>
+
+
+<dl>
+<dt>Source Code</dt>
+<dd>Libmicrohttpd
+can be found on the main GNU ftp server:
+<a
href="http://ftp.gnu.org/gnu/libmicrohttpd/";>http://ftp.gnu.org/gnu/libmicrohttpd/</a>
+(via HTTP) and
+<a
href="ftp://ftp.gnu.org/gnu/libmicrohttpd/";>ftp://ftp.gnu.org/gnu/libmicrohttpd/</a>
+(via FTP). It can also be found
+on the <a href="/prep/ftp.html">GNU mirrors</a>;
+please
+<a href="http://ftpmirror.gnu.org/libmicrohttpd/";>use
+a mirror</a> if possible.</dd>
+
+<dt>Debian .deb package</dt>
+<dd>
+The debian package can be downloaded from the <a
href="http://packages.debian.org/";>official debian archive</a>.
+The extract package can be found under Utilities and the library under
Libraries.
+The respective packages for libmicrohttpd are <a
href="http://packages.debian.org/extract";>extract</a>, <a
href="http://packages.debian.org/libmicrohttpd";>libmicrohttpd</a> and for
development <a
href="http://packages.debian.org/libmicrohttpd-dev";>libmicrohttpd-dev</a>.
+<a href="http://www.backports.org/";>Backports</a> for Debian Stable are also
available.
+</dd>
+
+<dt>Tar Package</dt>
+<dd>
+The latest version can be found on <a
href="http://ftpmirror.gnu.org/libmicrohttpd/";>GNU mirrors</a>.
+If the mirror does not work, you should be able to find them on the main FTP
server at
+<a
href="ftp://ftp.gnu.org/gnu/libmicrohttpd/";>ftp://ftp.gnu.org/gnu/libmicrohttpd/</a>.
<br>
-libmicrohttpd can be used without any dependencies; however,
-for SSL/TLS support we require
-<a href="http://www.gnupg.org/documentation/manuals/gcrypt/";>libgcrypt</a> and
-<a href="http://www.gnutls.org/";>libgnutls</a>.
-Furthermore, the testcases use <a
-href="http://curl.haxx.se/libcurl/";>libcurl</a>. Some extended
-testcases also use <a href="http://sam.zoy.org/zzuf/";>zzuf</a> and <a
-href="http://www.dest-unreach.org/socat/";>socat</a> (to simulate
-clients that violate the HTTP protocols). You can compile and use
-libmicrohttpd without installing <tt>libgcrypt</tt>, <tt>libgnutls</tt>,
<tt>libcurl</tt>, <tt>zzuf</tt> or
-<tt>socat</tt>.
-</p>
-<p >
-If you want to be notified about updates, subscribe to <a
-href="http://freshmeat.net/projects/libmicrohttpd/";>libmicrohttpd on
-freshmeat</a> A public mailinglist for libmicrohttpd is hosted at <a
-href="http://lists.gnu.org/mailman/listinfo/libmicrohttpd";>http://lists.gnu.org/mailman/listinfo/libmicrohttpd</a>.
-</p>
-<a name="using"></a>
-<h2>Using libmicrohttpd</h2>
-<p >
+Latest release is <a
href="http://ftpmirror.gnu.org/libmicrohttpd/libmicrohttpd-0.9.26.tar.gz";>libmicrohttpd-0.9.26.tar.gz</a>.
+</dd>
+
+<dt>Windows</dt>
+<dd>
+Latest Windows binary is <a
href="http://ftpmirror.gnu.org/libmicrohttpd/libmicrohttpd-0.5.23-w32.zip";>libmicrohttpd-0.9.17-w32.zip</a>.
+</dd>
+</dl>
+
+
+<h3 id="documentation">Documentation</h3>
+
+<p>
In addition to the brief documentation on this webpage, we
have various other forms of documentation available:
<dl>
<dt><a
href="https://gnunet.org/svn/libmicrohttpd/src/include/microhttpd.h";>microhttpd.h</a></dt>
<dd>This include file documents most of the API in detail.</dd>
<dt>Manual</dt>
- <dd>The libmicrohttpd manual is available as one document in
- <a href="microhttpd.pdf">pdf</a> and <a href="microhttpd.html">html</a>
- formats.</dd>
+ <dd><a href="manual/"A manul for Libmicrohttpd</a>
+ is available online, as is <a href="/manual/">documentation for most GNU
software</a>.
+ You may also find more information about
+ Libmicrohttpd
+ by running
+<em><a href="manual/extractor.html">info libmicrohttpd</a></em>
+or
+<em><a href="man3/libmicrohttpd.3.html">man libmicrohttpd</a></em>,
+or by looking at
+<em>/usr/share/doc/libmicrohttpd/</em>,
+<em>/usr/local/doc/libmicrohttpd/</em>,
+or similar directories on your system.
+</dd>
<dt>Tutorial</dt>
- <dd>The libmicrohttpd tutorial is available as one document in
+ <dd>The GNU Libmicrohttpd tutorial is available as one document in
<a href="tutorial.pdf">pdf</a> and <a href="tutorial.html">html</a>
formats.</dd>
<dt>Compatibility</dt>
<dd>API <a
href="http://upstream-tracker.org/versions/libmicrohttpd.html";>compatibility
report</a> comparing
most recent GNU libmicrohttpd versions</dd>
</dl>
-<p >
-The rest of this section gives a general overview.
+
+
+<h3 id="mail">Mailing lists</h3>
+
+<p>Libmicrohttpd uses the
+<a
href="https://lists.gnu.org/mailman/listinfo/libmicrohttpd";>libmicrohttpd</a>
+mailinglist to discuss all aspects of
+Libmicrohttpd,
+including support, development and enhancement requests, as well as bug
reports.
</p>
-<p >
+
+<p>Announcements about
+Libmicrohttpd
+and most other GNU software are made on
+<a href="http://lists.gnu.org/mailman/listinfo/info-gnu";>info-gnu</a>
+(<a href="http://lists.gnu.org/archive/html/info-gnu/";>archive</a>).
+If you only want to get notifications about Libmicrohttpd, we
+suggest you subscribe to the project at
+<a href="http://freshmeat.net/projects/libmicrohttpd/";>freshmeat</a>.
+</p>
+
+<p>
+Security reports that should not be made immediately public can be
+sent directly to <a href="http://grothoff.org/christian/";>the
+maintainer</a>. If there is no response to an urgent issue, you can
+escalate to the general
+<a href="http://lists.gnu.org/mailman/listinfo/security";>security</a>
+mailing list for advice.</p>
+
+
+
+<h3 id="contribute">Getting involved</h3>
+
+<p>Development of
+Libmicrohttpd,
+and GNU in general, is a volunteer effort, and you can contribute. For
+information, please read <a href="/help/">How to help GNU</a>. If you'd
+like to get involved, it's a good idea to join the discussion mailing
+list (see above).</p>
+
+<dl>
+
+<dt>Development</dt>
+
+<dd>Known bugs and open feature requests are tracked in
+ <a href="https://gnunet.org/bugs/";>our bugtracker</a>.
+ You need to sign up for a reporter account. Please make
+ sure you report bugs under <strong>libmicrohttpd</strong> and not
+ under any of the other projects.</dd>
+<dt>Subversion access</dt>
+<dd>
+You can access the current development version of libmicrohttpd using
+<pre>$ svn checkout https://gnunet.org/svn/libmicrohttpd</pre><br>
+Our website is kept at
+<pre>$ svn checkout https://gnunet.org/svn/libmicrohttpd-docs</pre><br>
+</dd>
+
+<dt>Maintainer</dt>
+<dd>Libextractor
+is currently being maintained by <a
href="http://grothoff.org/christian/";>Christian Grothoff</a>.</dd>
+</dl>
+
+
+<h3 id="quickintro">Quick Introduction</h3>
+
+<dl>
+
+<dt>Dependencies<dt>
+<dd>
+GNU Libmicrohttpd can be used without any dependencies; however,
+for SSL/TLS support we require
+<a href="http://www.gnupg.org/documentation/manuals/gcrypt/";>libgcrypt</a> and
+<a href="http://www.gnutls.org/";>libgnutls</a>.
+Furthermore, the testcases use <a
+href="http://curl.haxx.se/libcurl/";>libcurl</a>. Some extended
+testcases also use <a href="http://sam.zoy.org/zzuf/";>zzuf</a> and <a
+href="http://www.dest-unreach.org/socat/";>socat</a> (to simulate
+clients that violate the HTTP protocols). You can compile and use
+GNU Libmicrohttpd without installing <tt>libgcrypt</tt>, <tt>libgnutls</tt>,
<tt>libcurl</tt>, <tt>zzuf</tt> or
+<tt>socat</tt>.
+</dd>
+
+<dt>A minimal example</dt>
+<dd>
Before including the <tt>microhttpd.h</tt> header, you may need to
include the headers of your operating system that define the <tt>size_t</tt>,
<tt>fd_set</tt>, <tt>socklen_t</tt> and <tt>struct sockaddr</tt> data
@@ -117,9 +245,8 @@
the <tt>microhttpd.h</tt> header will attempt to include the
appropriate headers automatically, which may fail for more exotic
platforms.
-</p>
-<p>
-Here is a minimal example for GNU/Linux (included in the distribution):
+
+The following is a minimal example for GNU/Linux (included in the
distribution):
<pre>
#include <microhttpd.h>
#include <stdlib.h>
@@ -186,10 +313,9 @@
MHD_stop_daemon(d);
return 0;
}
-</pre>
-</p>
-<h3>Threading models</h3>
-<p >
+</dd>
+<dt>Threading models</dt>
+<dd>
The example above uses the simplest threading model,
<tt>MHD_USE_THREAD_PER_CONNECTION</tt>. In this model, MHD starts one
thread to listen on the port for new connections and then spawns a new
@@ -198,8 +324,7 @@
synchronization issues!) and may need to perform blocking operations
(such as extensive IO or running of code) to handle an individual
connection.
-</p>
-<p >
+<br>
The second threading model, <tt>MHD_USE_SELECT_INTERNALLY</tt>, uses
only a single thread to handle listening on the port and processing of
requests. This model is preferable if spawning a thread for each
@@ -236,8 +361,7 @@
<tt>MHD_USE_SELECT_INTERNALLY</tt> in combination with a thread pool
is typically the most scalable (but also hardest to debug) mode of
operation for MHD.
-</p>
-<p >
+<br>
The fourth threading model (used when no specific flag is given), uses
no threads. Instead, the main application must (periodically) request
file descriptor sets from MHD, perform a select call and then call
@@ -252,13 +376,12 @@
select loop to wake up and continue once the data is ready -- MHD will
unlist the socket from the write set if the application failed to
provide response data (this only happens in this mode).
-</p>
-<p >
+<br>
The testcases provided include examples for using each of the
threading modes.
-</p>
-<h3>Responses</h3>
-<p >
+</dd>
+<dt>Generating responses</dt>
+<dd>
MHD provides various functions to create <tt>struct MHD_Response</tt>
objects. A response consists of a set of HTTP headers and a (possibly
empty) body. The three main ways to create a response are either by
@@ -273,8 +396,7 @@
maybe too large to fit into memory. Finally, using a file descriptor
can be used on Linux systems to use the highly efficient
<tt>sendfile</tt> call for the file transfer.
-</p>
-<p >
+<br>
A response is used by calling <tt>MHD_queue_response</tt> which sends
the response back to the client on the specified connection. Once
created, a response object can be used any number of times.
@@ -286,9 +408,9 @@
the response will be immediately destroyed -- destruction may be
delayed until sending of the response is complete on all connections
that have the response in the queue.
-</p>
-<h3>Queueing responses</h3>
-<p >
+</dd>
+<dt>Queueing responses</dt>
+<dd>
Clients should never create a "100 CONTINUE" response. MHD
handles "100 CONTINUE" internally and only allows clients to
queue a single response per connection. Furthermore, clients must not
@@ -297,8 +419,7 @@
client attempts to queue multiple responses or attempts to queue a
response early, <tt>MHD_queue_response</tt> will fail (and return
<tt>MHD_NO</tt>).
-</p>
-<p >
+<br>
The callback function for the respective URL will be called at least
twice. The first call happens after the server has received the
headers. The client should use the last <tt>void**</tt> argument to
@@ -324,9 +445,9 @@
response depending on the threading model that is used. If the
callback does not queue a response at this point, MHD will either
(eventually) timeout the connection or keep calling it.
-</p>
-<h3>Parsing of POST requests</h3>
-<p >
+</dd>
+<dt>Parsing of POST requests</dt>
+<dd>
MHD includes a set of three functions for parsing and processing data
received in POST requests. The functions allow incremental parsing
and processing of POST data. Only a tiny fraction of the overall POST
@@ -336,9 +457,9 @@
of the received values. The POST parser itself is invoked repeatedly
whenever more input bytes become available. MHD supports both uri-
and multipart/form-encoded POST data.
-</p>
-<h3>Memory Management</h3>
-<p >
+</dd>
+<dt>Memory Management</dt>
+<dd>
The application can determine the size of buffers that MHD should use
for handling of HTTP requests and parsing of POST data. This way, MHD
users can trade-off processing time and memory utilization.
@@ -346,29 +467,12 @@
accept, as well as the total amount of memory used per connection.
MHD will gracefully handle all out-of-memory situations (by closing
the connection and cleaning up any remaining state).
-</p>
-<a name="mantis"></a>
-<h2>Bugtrack</h2>
-<p >
-libmicrohttpd uses Mantis for bugtracking. Visit <a
-href="https://gnunet.org/bugs/";>https://gnunet.org/bugs/</a> to
-report bugs. You need to sign up for a reporter account. Please make
-sure you report bugs under <strong>libmicrohttpd</strong> and not
-under any of the other projects.
-</p>
-<p >
-For questions and discussions please use the
-<a href="http://lists.gnu.org/mailman/listinfo/libmicrohttpd";>GNU
libmicrohttpd mailinglist</a>.
-Messages to the list from non-subscribers are subject to manual moderation
-and are hence likely to be delayed significantly.
-</p>
+</dd>
-<a name="users"></a>
-<h2>Applications using libmicrohttpd</h2>
-<p>
+<dt>Projects that use libmicrohttpd</dt>
+<dd>
If you write an application that uses libmicrohttpd, please
let us know so that we can add you to the list!
-</p>
<ul>
<li><a href="https://gnunet.org/";>GNUnet (P2P network)</a></li>
<li><a href="https://p4p.cs.yale.edu/download/portal.html";>P4P Portal</a></li>
@@ -395,13 +499,12 @@
<li><a href="http://www.opensips.org/";>OpenSIPs (HTTP transport layer via
httpd module)</a></li>
<li><a href="http://www.volkszaehler.org/";>volkszaehler (smart meter)</a></li>
</ul>
+</dd>
-<a name="alternatives"></a>
-<h2>Alternatives</h2>
-<p>
+<dt>Alternatives</dt>
+<dd>
If you are aware of a competing library that might be a better fit for
some developers, please let us know so that we can add it to the list!
-</p>
<ul>
<li><a href="http://www.pion.org/projects/pion-network-library";>Pion Network
Library (C++)</a></li>
<li><a href="http://www.hughes.com.au/products/libhttpd/";>libhttpd (C)</a></li>
@@ -418,22 +521,88 @@
<li><a href="https://github.com/abique/mimosa";>Mimosa (C++)</a></li>
<li><a href="https://github.com/ellzey/libevhtp/";>libevhtp (C)</a></li>
</ul>
+</dd>
-<a name="funding"></a>
-<h2>Funding</h2>
-<p>
-GNU libmicrohttpd development is currently funded in part by
-the <a href="http://www.dfg.de/";>Deutsche Forschungsgemeinschaft</a>
-under ENP GR 3688/1-1.
+</dl>
+
+<h3 id="license">Licensing</h3>
+
+<p>Libextractor
+is free software; you can redistribute it and/or modify it under the
+<a href="http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html";>GNU
+LGPL v2.1</a> or at your
+option <a href="http://www.gnu.org/licenses/lgpl.html";>any later
+version</a>. If you disable HTTPS/SSL support, you can also choose
+the second license,
+the <a href="http://ecos.sourceware.org/license-overview.html";>eCos
+License</a>. If you have questions about licensing, please contact
+the
+<a href="http://grothoff.org/christian/";>maintainer</a>.
</p>
-<hr/>
-<address><a href="mailto:address@hidden";>Christian Grothoff</a></address>
-<pre>
-Copyright (C) 2007, 2008, 2009, 2010, 2011 Christian Grothoff.
-Verbatim copying and distribution of this entire article
-is permitted in any medium, provided this notice is preserved.
-</pre>
-<br />
+
+
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p><!-- WEBMASTERS: Replace address@hidden with address@hidden and
+ remove this comment after completion. -->
+
+Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+
+<p>Copyright © 2012 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2013/03/28 09:00:55 $
+<!-- timestamp end -->
</p>
-</body></html>
+</div>
+</div>
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] r26662 - libmicrohttpd-docs/WWW,
gnunet <=