From 3a8ba90dfb0c2eb224f317dd692ede426691e72a Mon Sep 17 00:00:00 2001
From: Diego Nehab
@@ -70,8 +70,8 @@ local ftp = require("socket.ftp")
URLs MUST conform to -RFC -1738, that is, an URL is a string in the form: +RFC 1738, +that is, an URL is a string in the form:
diff --git a/doc/http.html b/doc/http.html index a274aef..66282a4 100644 --- a/doc/http.html +++ b/doc/http.html @@ -45,8 +45,7 @@ namespace offers full support for the client side of the HTTP protocol (i.e., the facilities that would be used by a web-browser implementation). The implementation conforms to the HTTP/1.1 standard, -RFC -2616. +RFC 2616.@@ -67,8 +66,7 @@ local http = require("socket.http")
URLs must conform to -RFC -1738, +RFC 1738, that is, an URL is a string in the form:
@@ -199,8 +197,7 @@ it usually returns a message body (a web page informing the URL was not found or some other useless page). To make sure the operation was successful, check the returned status code. For a list of the possible values and their meanings, refer to RFC -2616. +href="http://www.ietf.org/rfc/rfc2616.txt">RFC 2616.@@ -278,7 +275,7 @@ download and return status "401 Authentication Required". The HTTP/1.1 standard defines two authentication methods: the Basic Authentication Scheme and the Digest Authentication Scheme, both explained in detail in -RFC 2068. +RFC 2068.
The Basic Authentication Scheme sends @@ -304,7 +301,7 @@ b, c, h = http.request("http://fulano:silva@www.example.com/private/index.html") -- the request directly. r, c = http.request { url = "http://www.example.com/private/index.html", - headers = { authentication = "Basic " .. (mime.b64("fulano:silva")) } + headers = { authorization = "Basic " .. (mime.b64("fulano:silva")) } } diff --git a/doc/index.html b/doc/index.html index 5b54c59..665b97b 100644 --- a/doc/index.html +++ b/doc/index.html @@ -138,18 +138,22 @@ all!
+
- Fixed: manual sample of HTTP authentication now uses correct + "authorization" header (Alexandre Ittner); +
- Fixed: receive() returns immediatelly if prefix can satisfy + bytes requested (M Joonas Pihlaja);
- Fixed: multicast didn't work on Windows, or anywhere - else for that matter (Herbert Leuwer, Adrian Sietsma) + else for that matter (Herbert Leuwer, Adrian Sietsma);
- Fixed: select() now reports an error when called with more - sockets than FD_SETSIZE (Lorenzo Leonini) -
- Fixed: manual links to home.html changed to index.html (Robert Hahn) + sockets than FD_SETSIZE (Lorenzo Leonini); +
- Fixed: manual links to home.html changed to index.html (Robert Hahn);
- Fixed: mime.unb64() would return an empty string on results that started - with a null character (Robert Raschke) -
- Fixed: HTTP now automatically redirects on 303 and 307 (Jonathan Gray) + with a null character (Robert Raschke); +
- Fixed: HTTP now automatically redirects on 303 and 307 (Jonathan Gray);
- Fixed: calling sleep() with negative numbers could block forever, wasting CPU. Now it returns immediately (MPB);
- Improved: FTP commands are now sent in upper case to - help buggy servers (Anders Eurenius) + help buggy servers (Anders Eurenius);
- Improved: known headers now sent in canonic capitalization to help buggy servers (Joseph Stewart);
- Improved: Clarified tcp:receive() in the manual (MPB); diff --git a/doc/mime.html b/doc/mime.html index 9844744..ae136fd 100644 --- a/doc/mime.html +++ b/doc/mime.html @@ -44,11 +44,11 @@ content transfer encodings, such as Base64 and Quoted-Printable. It also provides functions to break text into lines and change the end-of-line convention. MIME is described mainly in -RFC 2045, -2046, -2047, -2048, and -2049. +RFC 2045, +2046, +2047, +2048, and +2049.
diff --git a/doc/smtp.html b/doc/smtp.html index 980b821..2ef673a 100644 --- a/doc/smtp.html +++ b/doc/smtp.html @@ -48,14 +48,13 @@ control (if you bother to read the code).
The implementation conforms to the Simple Mail Transfer Protocol, -RFC 2821. +RFC 2821. Another RFC of interest is RFC 2822, +href="http://www.ietf.org/rfc/rfc2822.txt">RFC 2822, which governs the Internet Message Format. Multipart messages (those that contain attachments) are part of the MIME standard, but described mainly -in RFC -2046 +in RFC 2046
In the description below, good understanding of LTN012, Filters @@ -196,7 +195,7 @@ part of the message and will not be sent to anyone.
-RFC 2822 +RFC 2822 has two important and short sections, "3.6.3. Destination address fields" and "5. Security considerations", explaining the proper use of these headers. Here is a summary of what it says: @@ -236,9 +235,9 @@ exactly what you don't want to happen!
I hope this clarifies the issue. Otherwise, please refer to -RFC 2821 +RFC 2821 and -RFC 2822. +RFC 2822.
diff --git a/doc/url.html b/doc/url.html index 303e05d..9f234d9 100644 --- a/doc/url.html +++ b/doc/url.html @@ -42,8 +42,7 @@ The url namespace provides functions to parse, protect, and build URLs, as well as functions to compose absolute URLs from base and relative URLs, according to -RFC -2396. +RFC 2396.@@ -91,7 +90,7 @@ The function returns a string with the absolute URL.
Note: The rules that govern the composition are fairly complex, and are described in detail in -RFC 2396. +RFC 2396. The example bellow should give an idea of what the rules are.
-- cgit v1.2.3-55-g6feb