Subversion. Fixing “could not read status line: connection was closed by server”By neokrates, written on March 23, 2010 |
 howto |
- neokrates
- Email: uwarov@yahoo.com
- Website: http://www.thinkplexx.com
- Join date: 05-31-09
- Posts: 20
Rate it
(No Ratings Yet)
Loading ...
Ad
Poll
Do you plan to migrate to new SCM?
- Our current SCM is just perfect (69%, 9 Votes)
- Subversion (SVN) (15%, 2 Votes)
- Git (8%, 1 Votes)
- Mercurial (Hg) (8%, 1 Votes)
- Bazaar (0%, 0 Votes)
- Other (0%, 0 Votes)
Total Voters: 13
Loading ...
Most popular search terms:
You are sure that repository working and can be accessed. You can see that SVN server is listening on given url. “Some” client get “some” kind of connection. But with other client you get “Could not read status line: connection was closed by server”. There is at least one simple way to connect that works in many cases…
| 1 |
Try different url PROTOCOL setting for connection string:
Try:
1 2 3 4 | svn co http://${YOUR_URL}/ svn co https://${YOUR_URL}/ svn co svn://${YOUR_URL}/ svn co svn+ssh://${YOUR_URL}/ |
Did one of those commands work. If yes, use this protocol everywhere.
| 2 |
Use working PROTOCOL for all other clients as well
|
LEARN MORE (amazon bookstore)
|
|
TAGS
|
|
RELATED
|
Pages
Posts
|
|
SOCIAL
|
|
Very helpful post man, thanks for the info.
Like or Dislike:
0 
0
[...] Could not read status line: connection was closed by server [...]
Like or Dislike:
0 
0
Very nice, Thanx
Like or Dislike:
0 
0