HTTPV2 compatibility issue with write through proxy setup

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All,

I use apache-2.2 on my laptop with latest trunk build of svn.

I use my local apache as a slave to a master repo which has svn-1.5.x
with apache-2.2.x.

When I commit to my slave it receives 500 Internal server response
thanks to new HTTPV2 code which checks for the HTTPV2 capability of the
slave *not* the master.

I am not sure about how to handle this case!, just thought of sharing
what I observed.

With regards
Kamesh Jayachandran
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJyL0/3WHvyO0YTCwRAgNKAJ4lF49T7hWXR2LymPPxluwxmvhV3QCglywF
mWSzyzv1iP+XIgjd+bTUn7E=
=2n7O
-----END PGP SIGNATURE-----

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1400639
Received on 2009-03-24 11:59:46 CET