ietf-nntp PAT

Clive D.W. Feather clive at demon.net
Tue Aug 15 11:09:41 PDT 2000


Russ Allbery said:
> If INN refuses to do the PAT search for some reason (such as the header
> not being in overview and not being willing to search articles on disk),
> PAT returns an error code *not* an empty successful response.

If we support this behaviour in PAT, it needs to be explicitly documented.
It should also have an error code that is *not* the usual 502 "not
permitted". I'm not sure if this is a suitable case for 503 (I'm looking at
502 and 503 separately), or if it should be something new, in which case I
would go for 521 but others might think 505 is better.

While I'm at it:

> See RFC-1036 for a
> list of valid header lines.

This implies that a server should reject any header line not in RFC 1036.
Is this the intention (I hope not) ? Or should PAT try to match any header
that it's given (simple and useful) ? Or should the *server* decide which
headers are allowed (see above) ?

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:  +44 20 8371 1138
Internet Expert     | Home:  <clive at davros.org>  | Fax:  +44 20 8371 1037
Demon Internet      | WWW: http://www.davros.org | DFax: +44 20 8371 4037
Thus plc            |                            | Mobile: +44 7973 377646 



More information about the ietf-nntp mailing list