@mark thx for the hint with the other list!
FYI here to this users_at_subversion.apache.org list ... i used the
Eclipse standard svn checkout UI (new svn project wizard) to select the
branch, so i would assume the URL is not the real problem ;-)
Server: Subversion 1.6.11 (r934486)
Here are some strange logentries from the apache error.log:
[Wed Jul 31 09:39:51 2013] [error] [client x.x.x.x] Could not fetch
resource information. [301, #0] [Wed Jul 31 09:39:51 2013] [error]
[client x.x.x.x] (17)File exists: Requests for a collection must have a
trailing slash on the URI. [301, #0] [Wed Jul 31 09:52:38 2013] [error]
[client x.x.x.x] request failed: error reading the headers [Wed Jul 31
09:52:49 2013] [error] [client x.x.x.x] Invalid URI in request
\xff\xfb\x18\xff\xfb'\xff\xfd\x01\xff\xfb\x03\xff\xfd\x03 GET / HTTP/1.0
... any suggestions?
Von: Mark Phippard [mailto:markphip_at_gmail.com]
Gesendet: Mittwoch, 31. Juli 2013 15:51
Betreff: Re: [Subclipse-users] Server 1.6 checkout problem
On Wed, Jul 31, 2013 at 4:08 AM, Wolfgang Pinitsch
We are still running an older svn server (1.6) and i was trying
to do a simple fresh checkout of my branch. All i get is this message:
checkout http://svn/xxx/test -r HEAD --depth=infinity --force
APR does not understand this error code
svn: Unable to connect to a repository at URL
svn: Error running context: The server sent an improper HTTP
I would first triple check that you are entering the right URL. Other
than that, I would guess this is a bug in Subversion 1.8. It uses a new
library for HTTP communication and there have been a lot of bugs
surfacing due to less common configurations such as proxy servers that
advertise support for HTTP/1.1 but then do not fully support it. The
old library apparently new how to deal with those issues better. Many
of the known bugs were fixed in SVN 1.8.1, but I have not seen this on
the mailing list.
I can say that it is not a general problem with an older server.
Subclipse is hosted on a SVN 1.6 server and we are able to checkout and
use it OK.
It would be great to have you gather more information that could be
reported on users_at_subversion.apache.org so that they could fix the
problem. Failing that, I would say to just uinstall this Subclipse
version and install the latest Subclipse 1.8.x version instead of 1.10.x
and you should be all set.
Received on 2013-07-31 16:23:41 CEST