Mercurial > noffle
changeset 479:0dca2ed29197 noffle
[svn] * docs/FAQ: Add entry about X-NOFFLE-Status: header and its possible
values.
author | bears |
---|---|
date | Wed, 29 Sep 2004 23:07:28 +0100 |
parents | 2d5fb05adbc3 |
children | 5d32ceec7f25 |
files | ChangeLog docs/FAQ |
diffstat | 2 files changed, 24 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog Wed Jul 28 17:18:45 2004 +0100 +++ b/ChangeLog Wed Sep 29 23:07:28 2004 +0100 @@ -1,3 +1,8 @@ +Wed Sep 29 2004 Jim Hague <jim.hague@acm.org> + +* docs/FAQ: Add entry about X-NOFFLE-Status: header and its possible + values. + Tue Mar 16 2004 Jim Hague <jim.hague@acm.org> * docs/noffle.1,src/noffle.c: When outputing the entire message base
--- a/docs/FAQ Wed Jul 28 17:18:45 2004 +0100 +++ b/docs/FAQ Wed Sep 29 23:07:28 2004 +0100 @@ -57,3 +57,22 @@ A: No. You cannot read groups that are not known to NOFFLE, or articles that NOFFLE has already expired. NOFFLE will not refetch expired articles. + +------------------------------------------------------------------------------- + +Q: What are the possible values of the X-NOFFLE-Status: header that + Noffle adds to messages? + +A: The X-NOFFLE-Status: header can contain one, two or all of the + following, separated by spaces: + + INTERESTING + - This message should be downloaded on the next fetch, if it has + not been downloaded already. + + NOT_DOWNLOADED + - The article has not yet been downloaded. + + RETRIEVING_FAILED + - An attempt was made to retrieve the article from upstream, but + the attempt failed.