mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-06-23 01:08:53 +00:00
Update more links from http: to https: in documentation and comments.
This commit is contained in:
david-sarah
@ -44,7 +44,7 @@ copies files from the local disk onto the decentralized filesystem. We later
|
||||
provide read-only access to those files, allowing users to recover them.
|
||||
There are several other applications built on top of the Tahoe-LAFS
|
||||
filesystem (see the `RelatedProjects
|
||||
<http://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects>`_ page of the
|
||||
<https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects>`_ page of the
|
||||
wiki for a list).
|
||||
|
||||
|
||||
@ -158,7 +158,7 @@ that doesn't match the capability you used to refer to that file. The
|
||||
filesystem layer (described below) adds human-meaningful names atop the
|
||||
key-value layer.
|
||||
|
||||
.. _`Zooko's Triangle`: http://en.wikipedia.org/wiki/Zooko%27s_triangle
|
||||
.. _`Zooko's Triangle`: https://en.wikipedia.org/wiki/Zooko%27s_triangle
|
||||
|
||||
|
||||
Server Selection
|
||||
|
||||
@ -10,7 +10,7 @@ to encrypted data.
|
||||
|
||||
(login required; username/password pairs available at `bugmenot`_).
|
||||
|
||||
.. _recently reported: http://www.nytimes.com/2010/09/27/us/27wiretap.html
|
||||
.. _recently reported: https://www.nytimes.com/2010/09/27/us/27wiretap.html
|
||||
.. _bugmenot: http://www.bugmenot.com/view/nytimes.com
|
||||
|
||||
Commentary by the `Electronic Frontier Foundation`_, `Peter Suderman /
|
||||
@ -30,8 +30,8 @@ exploitable by other parties (a notable example being the Greek cellphone
|
||||
eavesdropping scandal in 2004/5). RFCs `1984`_ and `2804`_ elaborate on the
|
||||
security case against such backdoors.
|
||||
|
||||
.. _1984: http://tools.ietf.org/html/rfc1984
|
||||
.. _2804: http://tools.ietf.org/html/rfc2804
|
||||
.. _1984: https://tools.ietf.org/html/rfc1984
|
||||
.. _2804: https://tools.ietf.org/html/rfc2804
|
||||
|
||||
Note that since Tahoe-LAFS is open-source software, forks by people other
|
||||
than the current core developers are possible. In that event, we would try to
|
||||
|
||||
@ -44,7 +44,7 @@ The item descriptions below use the following types:
|
||||
a Twisted listening-port specification string, like "``tcp:80``" or
|
||||
"``tcp:3456:interface=127.0.0.1``". For a full description of the format,
|
||||
see `the Twisted strports documentation
|
||||
<http://twistedmatrix.com/documents/current/api/twisted.application.strports.html>`_.
|
||||
<https://twistedmatrix.com/documents/current/api/twisted.application.strports.html>`_.
|
||||
Please note, if interface= is not specified, Tahoe-LAFS will attempt to
|
||||
bind the port specified on all interfaces.
|
||||
|
||||
|
||||
@ -189,7 +189,7 @@ isn't very useful except for testing.
|
||||
|
||||
For further information on SFTP compatibility and known issues with various
|
||||
clients and with the sshfs filesystem, see
|
||||
`<http://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend>`_.
|
||||
`<https://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend>`_.
|
||||
|
||||
Dependencies
|
||||
============
|
||||
@ -236,25 +236,25 @@ Known Issues
|
||||
============
|
||||
|
||||
Mutable files are not supported by the FTP frontend (`ticket #680
|
||||
<http://tahoe-lafs.org/trac/tahoe-lafs/ticket/680>`_). Currently, a directory
|
||||
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/680>`_). Currently, a directory
|
||||
containing mutable files cannot even be listed over FTP.
|
||||
|
||||
The FTP frontend sometimes fails to report errors, for example if an upload
|
||||
fails because it does meet the "servers of happiness" threshold (`ticket
|
||||
#1081 <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1081>`_). Upload errors
|
||||
#1081 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1081>`_). Upload errors
|
||||
also may not be reported when writing files using SFTP via sshfs (`ticket
|
||||
#1059 <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1059>`_).
|
||||
#1059 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1059>`_).
|
||||
|
||||
Non-ASCII filenames are not supported by FTP (`ticket #682
|
||||
<http://tahoe-lafs.org/trac/tahoe-lafs/ticket/682>`_). They can be used with
|
||||
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/682>`_). They can be used with
|
||||
SFTP only if the client encodes filenames as UTF-8 (`ticket #1089
|
||||
<http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1089>`_).
|
||||
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1089>`_).
|
||||
|
||||
The gateway node may hang or consume 100% CPU if the client tries to rekey.
|
||||
(`ticket #1297 <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1297>`_). This
|
||||
is due to `a bug in Twisted <http://twistedmatrix.com/trac/ticket/4395>`_
|
||||
(`ticket #1297 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1297>`_). This
|
||||
is due to `a bug in Twisted <https://twistedmatrix.com/trac/ticket/4395>`_
|
||||
which was fixed in Twisted 11.0 (released 3-April-2011).
|
||||
|
||||
For options to disable rekeying in various clients in order to work around
|
||||
this issue, and for other known issues in SFTP, see
|
||||
`<http://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend>`_.
|
||||
`<https://tahoe-lafs.org/trac/tahoe-lafs/wiki/SftpFrontend>`_.
|
||||
|
||||
@ -21,7 +21,7 @@ document is to explain what it all means. It was written by Brian
|
||||
Warner, who wrote the v1.8.0 downloader code and the code which
|
||||
generates this status report about the v1.8.0 downloader's
|
||||
behavior. Brian posted it to the trac:
|
||||
http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1169#comment:1
|
||||
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1169#comment:1
|
||||
|
||||
Then Zooko lightly edited it while copying it into the docs/
|
||||
directory.
|
||||
|
||||
@ -130,11 +130,11 @@ Unicode names are supported, but the local name of a file must be encoded
|
||||
correctly in order for it to be uploaded. The expected encoding is that
|
||||
printed by ``python -c "import sys; print sys.getfilesystemencoding()"``.
|
||||
|
||||
.. _`#1105`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1105
|
||||
.. _`#1430`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1430
|
||||
.. _`#1431`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1431
|
||||
.. _`#1432`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1432
|
||||
.. _`#1433`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1433
|
||||
.. _`#1449`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1449
|
||||
.. _`#1458`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1458
|
||||
.. _`#1459`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1459
|
||||
.. _`#1105`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1105
|
||||
.. _`#1430`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1430
|
||||
.. _`#1431`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1431
|
||||
.. _`#1432`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1432
|
||||
.. _`#1433`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1433
|
||||
.. _`#1449`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1449
|
||||
.. _`#1458`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1458
|
||||
.. _`#1459`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1459
|
||||
|
||||
@ -52,7 +52,7 @@ This string is actually a Twisted "strports" specification, meaning you can
|
||||
get more control over the interface to which the server binds by supplying
|
||||
additional arguments. For more details, see the documentation on
|
||||
`twisted.application.strports
|
||||
<http://twistedmatrix.com/documents/current/api/twisted.application.strports.html>`_.
|
||||
<https://twistedmatrix.com/documents/current/api/twisted.application.strports.html>`_.
|
||||
|
||||
Writing "tcp:3456:interface=127.0.0.1" into the web.port line does the same
|
||||
but binds to the loopback interface, ensuring that only the programs on the
|
||||
@ -74,7 +74,7 @@ with it (such as read or modify the contents). This identifier is called a
|
||||
"read-cap" or "write-cap", depending upon whether it enables read-only or
|
||||
read-write access. These "caps" are also referred to as URIs (which may be
|
||||
confusing because they are not currently `RFC3986
|
||||
<http://tools.ietf.org/html/rfc3986>`_-compliant URIs).
|
||||
<https://tools.ietf.org/html/rfc3986>`_-compliant URIs).
|
||||
|
||||
The Tahoe web-based API is "REST-ful", meaning it implements the concepts of
|
||||
"REpresentational State Transfer": the original scheme by which the World
|
||||
@ -2047,7 +2047,7 @@ the ``logs/twistd.log`` file.
|
||||
|
||||
HTTP does not provide a mechanism to specify the character set used to
|
||||
encode non-ASCII names in URLs
|
||||
(`RFC3986#2.1 <http://tools.ietf.org/html/rfc3986#section-2.1>`_).
|
||||
(`RFC3986#2.1 <https://tools.ietf.org/html/rfc3986#section-2.1>`_).
|
||||
We prefer the convention that the ``filename=`` argument shall be a
|
||||
URL-escaped UTF-8 encoded Unicode string.
|
||||
For example, suppose we want to provoke the server into using a filename of
|
||||
@ -2075,14 +2075,14 @@ the ``logs/twistd.log`` file.
|
||||
(note, the last four bytes of that line, not including the newline, are
|
||||
0xC3 0xA9 0x65 0x22)
|
||||
|
||||
`RFC2231#4 <http://tools.ietf.org/html/rfc2231#section-4>`_
|
||||
`RFC2231#4 <https://tools.ietf.org/html/rfc2231#section-4>`_
|
||||
(dated 1997): suggests that the following might work, and
|
||||
`some developers have reported <http://markmail.org/message/dsjyokgl7hv64ig3>`_
|
||||
that it is supported by Firefox (but not IE7)::
|
||||
|
||||
#2: Content-Disposition: attachment; filename*=utf-8''fianc%C3%A9e
|
||||
|
||||
My reading of `RFC2616#19.5.1 <http://tools.ietf.org/html/rfc2616#section-19.5.1>`_
|
||||
My reading of `RFC2616#19.5.1 <https://tools.ietf.org/html/rfc2616#section-19.5.1>`_
|
||||
(which defines Content-Disposition) says that the filename= parameter is
|
||||
defined to be wrapped in quotes (presumably to allow spaces without breaking
|
||||
the parsing of subsequent parameters), which would give us::
|
||||
|
||||
@ -3,11 +3,11 @@
|
||||
Below is a list of known issues in older releases of Tahoe-LAFS, and how to
|
||||
manage them. The current version of this file can be found at
|
||||
|
||||
http://tahoe-lafs.org/source/tahoe/trunk/docs/historical/historical_known_issues.txt
|
||||
https://tahoe-lafs.org/source/tahoe/trunk/docs/historical/historical_known_issues.txt
|
||||
|
||||
Issues in newer releases of Tahoe-LAFS can be found at:
|
||||
|
||||
http://tahoe-lafs.org/source/tahoe/trunk/docs/known_issues.rst
|
||||
https://tahoe-lafs.org/source/tahoe/trunk/docs/known_issues.rst
|
||||
|
||||
== issues in Tahoe v1.8.2, released 30-Jan-2011 ==
|
||||
|
||||
@ -177,7 +177,7 @@ mutable files, you may be able to avoid the potential for "rollback"
|
||||
failure.
|
||||
|
||||
A future version of Tahoe will include a fix for this issue. Here is
|
||||
[http://tahoe-lafs.org/pipermail/tahoe-dev/2008-May/000630.html the
|
||||
[https://tahoe-lafs.org/pipermail/tahoe-dev/2008-May/000630.html the
|
||||
mailing list discussion] about how that future version will work.
|
||||
|
||||
|
||||
|
||||
@ -153,9 +153,9 @@ Opera also has a similar facility that is disabled by default. A previous
|
||||
version of this file stated that Firefox had abandoned their phishing
|
||||
filter; this was incorrect.
|
||||
|
||||
.. _a brief description of their filter's operation: http://blogs.msdn.com/ie/archive/2005/09/09/463204.aspx
|
||||
.. _"safe browsing API": http://code.google.com/apis/safebrowsing/
|
||||
.. _specification: http://code.google.com/p/google-safe-browsing/wiki/Protocolv2Spec
|
||||
.. _a brief description of their filter's operation: https://blogs.msdn.com/ie/archive/2005/09/09/463204.aspx
|
||||
.. _"safe browsing API": https://code.google.com/apis/safebrowsing/
|
||||
.. _specification: https://code.google.com/p/google-safe-browsing/wiki/Protocolv2Spec
|
||||
.. _Firefox bugzilla ticket #368255: https://bugzilla.mozilla.org/show_bug.cgi?id=368255
|
||||
|
||||
|
||||
|
||||
@ -277,14 +277,14 @@ and dozens of others.
|
||||
This manpage was originally written by bertagaz.
|
||||
.SH REPORTING BUGS
|
||||
.PP
|
||||
Please see <http://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug>.
|
||||
Please see <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug>.
|
||||
.PP
|
||||
For known security issues see
|
||||
<http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst>.
|
||||
<https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst>.
|
||||
.PP
|
||||
Tahoe-LAFS home page: <http://tahoe-lafs.org/>
|
||||
Tahoe-LAFS home page: <https://tahoe-lafs.org/>
|
||||
.PP
|
||||
tahoe-dev mailing list: <http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>
|
||||
tahoe-dev mailing list: <https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>
|
||||
.SH COPYRIGHT
|
||||
.PP
|
||||
Copyright \@ 2006\[en]2012 The Tahoe-LAFS Software Foundation
|
||||
|
||||
Reference in New Issue
Block a user