[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: checkout, update, and commit are slow using WinXP client with a WebDav repo

From: Erik Pilz <epilz_at_altastrada.com>
Date: 2006-07-13 22:31:37 CEST

I have a bit more info on this issue that might help.

 From the mailing list archives a Server 400 ("Bad Request") response is
usually caused by a proxy or firewall that doesn't allow REPORT
requests. To test if this is a firewall/proxy issue I decided to take my
laptop to the office. I also disabled the Windows firewall and the
anti-virus software to make sure that they aren't interfering.
Unfortunately, the problem still occurred.

Since my office computer (an almost identical configuration) is able to
successfully checkout the repository, I think it's safe to say that it
is a problem that is specific to the laptop.

I also tried to determine if perhaps there's a physical problem with the
network interface on the laptop. To do this I connected using the WiFi
interface and even a modem and found that the problem still occurs on
those interfaces.

There was one interesting find as I was troubleshooting this problem.
Checking out a WebDav repository that is served over HTTPS doesn't
exhibit the issue.

Again, I'd appreciate any help figuring this one out.


Erik Pilz wrote:
> Hello there. I'm looking for a bit of help troubleshooting a WinXP
> client problem. Executing any of the "checkout," "update," and "commit"
> commands against a WebDav repository is really slow (e.g., checking out
> a small repository takes about 7-8 minutes). The requests never fail,
> they just take a really long time to complete. I don't have any problems
> working with repositories that use the svn network protocal, just ones
> that use WebDav.
> I've tried a few different versions of the SVN client for WinXP,
> TortoiseSVN, and Subclipse. All exhibit the same problem. Currently, I'm
> working with the SVN command line client, version 1.3.2 (r19776) on a
> machine running WinXP SP2 (with all current patches).
> I ran Ethereal to capture some information about the conversation.
> Here's the only interesting HTTP request that I noticed:
> --- Begin Ethereal Snip ---
> REPORT /qed/!svn/vcc/default HTTP/1.1\r\n
> Host: svn.pilzner.com
> User-Agent: SVN/1.3.2 (r19776) neon/0.25.5
> Connection: TE
> TE: trailers
> Content-Type: text/xml
> Accept-Encoding: gzip
> Accept-Encoding: gzip
> <S:update-report send-all="true"
> xmlns:S="svn:"><S:src-path>http://svn.pilzner.com/qed</S:src-path>
> <S:target-revision>3</S:target-revision><S:entry rev="3"
> start-empty="true"></S:entry></S:update-report
> --- End Ethereal Snip ---
> When the server receives the request it responds with a 400 status code
> (bad request). I'm assuming that this happens because the XML body isn't
> well-formed (the right angle bracket to close the <S:update-report>
> element is missing). The other interesting thing about this request is
> that after this there's no network traffic for several minutes.
> Eventually the SVN client re-sends the request with a well-formed XML
> body and the server responds with a status code of 200. The SVN command
> then succeeds.
> I'd appreciate any help troubleshooting this.
> Thanks,
> Erik
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 13 22:33:01 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.