Out of office: jcoffey-dev is traveling from November 1 to November 6. Responses to issues may be slow or delayed during this time, but I will be checking in.
An addressbook-query or other DAV REPORT asking for <nresults>0</nresults>
started its countdown of results at zero and subtracted from it after
the first result, wrapping it around to the largest number: the
configured maximum number of results no longer applied, so one request
could return every item of the collection. Debug builds panicked in the
request handler instead. Any signed-in user could send it.
A limit of zero is now treated as one, and the message for an exceeded
limit names the limit actually applied.
Test: webdav card_query.rs, an addressbook-query with nresults 0 hit
"attempt to subtract with overflow" at propfind.rs and the connection
closed on main; now one result and the 507 number-of-matches-within-
limits response naming a limit of 1.