Step 7 of section 4.3 reads:
Let headers be the names of request's author headers, sorted
lexicographically and [[byte lowercased]].
Isn't the phrase "byte lowercased" rather easy to define, since each author
header can only
contain ASCII characters? Maybe it should be:
7. Let headers be the names of request's author headers.
7a. For each name in headers, convert that name to ASCII lowercase, and
convert that name to a byte
array by changing each code point to the corresponding byte.
7b. Sort headers in ascending order using a byte-for-byte comparison.
---------------------
FTP Responses
One issue box says "Map the result to response." What exactly is the issue
with mapping the result?
Should the response, including errors, be mapped to HTTP responses somehow?
Should FTP
errors (4xx and 5xx) be treated as "network errors"?
Also, the text “Follow the requirements from FTP to retrieve a resource” is
rather vague. It seems
that’s because it takes more steps to retrieve a file via FTP than via HTTP.
Implementations that don’t
have a higher-level FTP backend may find it harder to understand what those
steps consist of. Here is what I
think are the steps.
- Connect to server
- If URL has username, send USER [username]
- If URL has password, send PASS [password]
- Send TYPE I (binary mode)
- Send CWD [path]
- Send RETR [filename]
- Send QUIT
Moreover, if the FTP URL points to merely a directory, it’s unspecified what
kind of resource should be returned.
Maybe a list of files (LIST or NLST command)?
--Peter
