propfind yields inconsistent results between depth 1 on a collection and depth 0 on each of it's children

[dreid@…]

Performing a propfind for quota-used-bytes on /calendars/users/ with depth 1 yields the following response:

<response xmlns="DAV:">
  <href>/calendars/users/bob/</href>
  <propstat>
     <prop>
       <quota-available-bytes>104857600</quota-available-bytes>
       <quota-used-bytes>0</quota-used-bytes>
       <getetag>&quot;F42B5B-108-45526E13&quot;</getetag>
       <resourcetype><collection></collection></resourcetype>
       <displayname>bob</displayname>
     </prop>
     <status>HTTP/1.1 200 OK</status>
  </propstat>
</response>

A propfind with depth 0 on /calendars/users/bob/ yields a different result for quota-used-bytes

<response xmlns="DAV:">
  <href>/calendars/users/bob/</href>
  <propstat>
  <prop>
    <quota-available-bytes>104848783</quota-available-bytes>
    <quota-used-bytes>8817</quota-used-bytes>
    <getetag>&quot;F42B5B-108-45526E13&quot;</getetag>
    <resourcetype><collection></collection></resourcetype>
    <displayname>bob</displayname>
  </prop>
  <status>HTTP/1.1 200 OK</status>
  </propstat>
</response>

I'm unsure if this is specific to the quota-used-bytes property or if it could affect others.

[cdaboo@…]

Fixed in r1555. Tests in r1554.