You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Kamesh Jayachandran <ka...@collab.net> on 2009/03/24 11:00:15 UTC
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
Re: HTTPV2 compatibility issue with write through proxy setup
Posted by "C. Michael Pilato" <cm...@collab.net>.
Kamesh Jayachandran wrote:
>
>
> C. Michael Pilato wrote:
>> Kamesh Jayachandran wrote:
>>> 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.
>> Maybe we should re-add the HTTP configury that disables HTTP v2, so folks
>> with 1.7 masters and pre-1.7 slaves can still groove to the same beat?
>
>
> Hope you meant 1.7 slaves and pre-1.7 masters?
Oops -- yes! That's what I meant.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1402315
Re: HTTPV2 compatibility issue with write through proxy setup
Posted by Kamesh Jayachandran <ka...@collab.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
C. Michael Pilato wrote:
> Kamesh Jayachandran wrote:
>> 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.
>
> Maybe we should re-add the HTTP configury that disables HTTP v2, so folks
> with 1.7 masters and pre-1.7 slaves can still groove to the same beat?
>
Hope you meant 1.7 slaves and pre-1.7 masters?
With regards
Kamesh Jayachandran
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJyOVw3WHvyO0YTCwRAvr0AKCDGiy6MV2sunzVEyz/si2nhzA3JgCgjN3l
N3AXRv1bBjuWYCFleGLRt/0=
=oSQV
-----END PGP SIGNATURE-----
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1402306
Re: HTTPV2 compatibility issue with write through proxy setup
Posted by Kamesh Jayachandran <ka...@collab.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
C. Michael Pilato wrote:
> C. Michael Pilato wrote:
>> Kamesh Jayachandran wrote:
>>> 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.
>> Maybe we should re-add the HTTP configury that disables HTTP v2, so folks
>> with 1.7 masters and pre-1.7 slaves can still groove to the same beat?
>
> I re-added the SVNAdvertiseV2Protocol mod_dav_svn directive (defaulting to
> 'on' this time) in r37642.
>
> There's a part of me that thinks that this is a touch of madness -- is it
> really too much to ask of WebDAV proxy implementors that they have machine
> minor versions of Subversion across their whole server collection?
>
May not be, if I want to use my local laptop(having svn of current trunk
code) as a proxy against some of the pubic svn repositories, I am at
loss due to new protocol changes which 'public svn repositories' are
not aware of and hence write through would fail.
With regards
Kamesh Jayachandran
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFKA2NE3WHvyO0YTCwRArlTAJ90KVyIv9hBmVp/V3+Q3OfruNGtAgCdE42s
7Zz9mX1nvvMZ5KijWgd+C8Y=
=C+MQ
-----END PGP SIGNATURE-----
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2100918
Re: HTTPV2 compatibility issue with write through proxy setup
Posted by "C. Michael Pilato" <cm...@collab.net>.
C. Michael Pilato wrote:
> Kamesh Jayachandran wrote:
>> 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.
>
> Maybe we should re-add the HTTP configury that disables HTTP v2, so folks
> with 1.7 masters and pre-1.7 slaves can still groove to the same beat?
I re-added the SVNAdvertiseV2Protocol mod_dav_svn directive (defaulting to
'on' this time) in r37642.
There's a part of me that thinks that this is a touch of madness -- is it
really too much to ask of WebDAV proxy implementors that they have machine
minor versions of Subversion across their whole server collection?
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2098682
Re: HTTPV2 compatibility issue with write through proxy setup
Posted by "C. Michael Pilato" <cm...@collab.net>.
Kamesh Jayachandran wrote:
> 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.
Maybe we should re-add the HTTP configury that disables HTTP v2, so folks
with 1.7 masters and pre-1.7 slaves can still groove to the same beat?
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1402264