> This is fairly minor, but it's leading to a lot of unnecessary extra
> network traffic.
>
> If Xref is defined as part of the overview.fmt set, whenever an Xref header
> isn't seen, nntpcached is running an xpath request on the article.
>
> Xref is normally _only_ seen if an article is crossposted, so lack of Xref
> header is normal and indicates single-group posting, not a need to go grab
> more info.
>
> Has anyone looked at patching this slightly bogus behaviour?
>
> AB
This is intentional behavior (article.c):
if (!xref && getbyid)
{
log (("no Xref header or article number, trying xpath <%s>", msg
id));
If the article was fetched by <msgid>, and had no Xref: header,
then nntpcache has no key on which to cache the article for future
ARTICLE msg_number style references. It resolves this by using
xpath to get the article number.
Cheers,
Julian.
