firstname.lastname@example.org (John Franks) writes:
> Proposal for an HTTP MGET Method
[Design Objectives omitted]
1) Consider authentication. Suppose the server requires authentication
for one or more of the URL's in the MGET. What would the
interaction(s) between client and server look like? Consider,
particularly, what happens if some of the elements of the MGET fall
into different protection realms and thus require different methods of
authentication (or different username/passwords, to keep the discussion
2) I would like to see a definition of Content-type-encoding: packet.
Specifically, which bytes are included in the byte count? CRLF's? Is
the data uuencoded? Or are the bytes assumed to be binary data? I'm
asking for clarity because, if clients and servers get out of sync with
the counts on the MGET response, the result at the client side will be
a real mess.