With all due respect, the proposed solution looks enormous compared to the size of the problem. Does the original problem exist in HTTPv2? At a minimum, could the ra_dav providers not annotate the PROPFIND as "dont-proxy-this" without even touching the RA (and higher) APIs?
I *think* neon still uses the old protocol i.e do not make POST requests so suffers from original PROPFIND problem and hence need our fix.
*serf* uses 'POST' request to get the baseline revision, 'POST' request is proxied to MASTER so it does not suffer from this problem.
With regards Kamesh Jayachandran
