On Tue, Jun 18, 2013 at 10:38 AM, Branko Čibej <brane_at_wandisco.com> wrote:
> On 18.06.2013 16:34, Mark Phippard wrote:
>> On Tue, Jun 18, 2013 at 10:25 AM, Philip Martin
>> <philip.martin_at_wandisco.com> wrote:
>>> Mark Phippard <markphip_at_gmail.com> writes:
>>>
>>>> I also created a test project on tigris. So far, all commits are
>>>> working for that project -- which I guess is good news. Maybe some
>>>> odd scenario I am running into.
>>>>
>>>> I am just committing some new files though, so not sure what I am
>>>> doing that would be "weird".
>>> I don't see any "failing" requests. I see:
>>>
>>> PROPFIND /svn/subclipse/trunk/www/update_1.10.x HTTP/1.1
>>> HTTP/1.1 207 Multi-Status
>>> MKACTIVITY /svn/subclipse/!svn/act/5ea43b8a-0d4e-4ef0-8c62-5be2e0291f8e HTTP/1.1
>>> HTTP/1.1 201 Created
>>> PROPFIND /svn/subclipse/trunk/www/update_1.10.x HTTP/1.1
>>> HTTP/1.1 207 Multi-Status
>>> CHECKOUT /svn/subclipse/!svn/vcc/default HTTP/1.1
>>> HTTP/1.1 201 Created
>>> PROPPATCH /svn/subclipse/!svn/wbl/5ea43b8a-0d4e-4ef0-8c62-5be2e0291f8e/5706 HTTP/1.1
>>> HTTP/1.1 207 Multi-Status
>>> CHECKOUT /svn/subclipse/!svn/ver/5706/trunk/www/update_1.10.x HTTP/1.1
>>> HTTP/1.1 201 Created
>>> HEAD /svn/subclipse/trunk/www/update_1.10.x/artifacts.jar HTTP/1.1
>>> HTTP/1.1 404 Not Found
>>> HEAD /svn/subclipse/trunk/www/update_1.10.x/content.jar HTTP/1.1
>>> HTTP/1.1 404 Not Found
>>> CHECKOUT /svn/subclipse/!svn/ver/5706/trunk/www/update_1.10.x/features HTTP/1.1
>>> HTTP/1.1 201 Created
>>> DELETE /svn/subclipse/!svn/act/5ea43b8a-0d4e-4ef0-8c62-5be2e0291f8e HTTP/1.1
>>> HTTP/1.1 204 No Content
>>>
>>> Which all looks OK until the DELETE. A v1 commit done locally looks like:
>>>
>>> "PROPFIND /obj/repo/trunk/www/update_1.10.x HTTP/1.1" 207 722 Length:-
>>> "MKACTIVITY /obj/repo/!svn/act/a0a022ce-26d5-4934-bce4-ea8e6a66ad2b HTTP/1.1" 201 227 Length:-
>>> "PROPFIND /obj/repo/trunk/www/update_1.10.x HTTP/1.1" 207 430 Length:-
>>> "CHECKOUT /obj/repo/!svn/vcc/default HTTP/1.1" 201 241 Length:-
>>> "PROPPATCH /obj/repo/!svn/wbl/a0a022ce-26d5-4934-bce4-ea8e6a66ad2b/4 HTTP/1.1" 207 517 Length:-
>>> "CHECKOUT /obj/repo/!svn/ver/4/trunk/www/update_1.10.x HTTP/1.1" 201 263 Length:-
>>> "HEAD /obj/repo/trunk/www/update_1.10.x/artifacts.jar HTTP/1.1" 404 - Length:-
>>> "HEAD /obj/repo/trunk/www/update_1.10.x/contents.jar HTTP/1.1" 404 - Length:-
>>> "CHECKOUT /obj/repo/!svn/ver/4/trunk/www/update_1.10.x/features HTTP/1.1" 201 272 Length:-
>>> "HEAD /obj/repo/trunk/www/update_1.10.x/features/org.tigris.subversion.clientadapter.feature_1.10.0.jar HTTP/1.1" 404 - Length:-
>>> "PUT /obj/repo/!svn/wrk/a0a022ce-26d5-4934-bce4-ea8e6a66ad2b/trunk/www/update_1.10.x/contents.jar HTTP/1.1" 201 264 Length:-
>>> "PUT /obj/repo/!svn/wrk/a0a022ce-26d5-4934-bce4-ea8e6a66ad2b/trunk/www/update_1.10.x/artifacts.jar HTTP/1.1" 201 265 Length:-
>>> "PUT /obj/repo/!svn/wrk/a0a022ce-26d5-4934-bce4-ea8e6a66ad2b/trunk/www/update_1.10.x/features/org.tigris.subversion.clientadapter.feature_1.10.0.jar HTTP/1.1" 201 315 Length:-
>>> "MERGE /obj/repo/trunk/www/update_1.10.x HTTP/1.1" 200 2030 Length:-
>>> "DELETE /obj/repo/!svn/act/a0a022ce-26d5-4934-bce4-ea8e6a66ad2b HTTP/1.1" 204 - Length:-
>>>
>>> so all the requests you show appeared to work. The client should have
>>> gone on to do HEAD, PUT, PUT, PUT but something caused it to abort the
>>> commit and send a DELETE instead.
>> Agreed, it is very weird, not even sure where to look. Not only did I
>> consistently get this problem on repeated attempts to commit, but I
>> switched from Windows to Mac, did a new checkout and got same error
>> when trying to commit again.
>>
>> I needed to do this commit, so I have since done it using 1.7 and
>> Neon. 1.7 and Serf failed with APR error code unknown, which I assume
>> was the "The server sent a truncated HTTP response body" error.
>
> Might there possibly be an HTTP/1.0 proxy at work here?
If there is, it would have to be on tigris itself. Mike Pilato could
probably answer that better. I think it is mostly a plain (although
old) Apache + SVN. The authentication and authorization stuff is
custom. I do not think there is any proxy involved.
Mike would probably have better luck than me knowing how to get any
errors logged on the server as well.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2013-06-18 16:43:25 CEST