getetag should response with (empty) multistatus instead of 405 on scheudle inbox

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Send a REPORT to
https://www.google.com/calendar/dav/kewisch.moz%40gmail.com/inbox/

<?xml version="1.0" encoding="UTF-8"?>
<C:calendar-query xmlns:D="DAV:"
                  xmlns:C="urn:ietf:params:xml:ns:caldav">
  <D:prop>
    <D:getetag/>
  </D:prop>
  <C:filter>
    <C:comp-filter name="VCALENDAR">
      <C:comp-filter name="VEVENT"/>
    </C:comp-filter>
  </C:filter>
</C:calendar-query>

What is the expected output? What do you see instead?

I instead see a 405 Method not allowed respose, I'd expect an empty
multistatus, since you say the scheduling inbox is always empty, or maybe a
multistatus that contains a 404 telling the client that the prop was not found.

Original issue reported on code.google.com by kewi...@gmail.com on 20 Aug 2008 at 8:03

[GoogleCodeExporter]

I believe the server response 405 would be technically valid according to the 
CalDAV
Scheduling draft if the server didn't send "calendar-access" keyword in the DAV:
header for the particular resource (which it does). 

Original comment by filip.na...@gmail.com on 21 Aug 2008 at 10:00