Hi ! When i am trying to access svn over http i get this : [subhodip@home-server ~]$ svn co http://josm.openstreetmap.de/svn/trunk JOSM svn: REPORT request failed on '/svn/!svn/vcc/default' svn: REPORT of '/svn/!svn/vcc/default': 400 Bad Request (http://josm.openstreetmap.de)
While when i am doing this : [subhodip@home-server ~]$ svn co svn://svn.mapnik.org/trunk mapnik Checked out revision 697.
Why is this so ? what I am missing out here ?
2008/5/6 Subhodip Biswas subhodipbiswas@gmail.com:
Hi ! When i am trying to access svn over http i get this : [subhodip@home-server ~]$ svn co http://josm.openstreetmap.de/svn/trunk JOSM svn: REPORT request failed on '/svn/!svn/vcc/default' svn: REPORT of '/svn/!svn/vcc/default': 400 Bad Request (http://josm.openstreetmap.de)
Does this work: [subhodip@home-server ~]$ svn co svn://josm.openstreetmap.de/svn/trunk JOSM
Cheerio, Debarshi
When i am trying to access svn over http i get this : [subhodip@home-server ~]$ svn co http://josm.openstreetmap.de/svn/trunk JOSM svn: REPORT request failed on '/svn/!svn/vcc/default' svn: REPORT of '/svn/!svn/vcc/default': 400 Bad Request (http://josm.openstreetmap.de)
svn co http://josm.openstreetmap.de/svn/trunk JOSM just worked for me.
Cheerio, Debarshi
On 06-May-08, at 7:18 PM, Subhodip Biswas wrote:
When i am trying to access svn over http i get this : [subhodip@home-server ~]$ svn co http://josm.openstreetmap.de/svn/ trunk JOSM svn: REPORT request failed on '/svn/!svn/vcc/default' svn: REPORT of '/svn/!svn/vcc/default': 400 Bad Request (http://josm.openstreetmap.de)
works for me. Either your ISP is b0rked or some proxy is blocking svn over http. Some braindead sysadmins only allow svn over https
On Wed, May 7, 2008 at 12:53 PM, Kenneth Gonsalves lawgon@au-kbc.org wrote:
On 06-May-08, at 7:18 PM, Subhodip Biswas wrote:
When i am trying to access svn over http i get this : [subhodip@home-server ~]$ svn co http://josm.openstreetmap.de/svn/ trunk JOSM svn: REPORT request failed on '/svn/!svn/vcc/default' svn: REPORT of '/svn/!svn/vcc/default': 400 Bad Request (http://josm.openstreetmap.de)
works for me. Either your ISP is b0rked or some proxy is blocking svn over http. Some braindead sysadmins only allow svn over https
s/svn/WebDAV/g
The correct term to use here would be WebDAV over http (instead of svn over http). I suppose the reason for blocking would be that WebDAV is an extension of the http protocol. It adds certain methods like PROPFIND, COPY etc. So if your ISP blocks anything other than the basic HTTP methods (get,post, head,put,delete,options,trace) it will block WebDAV.
https is generally transparently proxied, so that should solve your problem.
-- regards
Kenneth Gonsalves Associate, NRC-FOSS lawgon@au-kbc.org http://nrcfosshelpline.in/code/
2008/5/7 Puneet Lakhina puneet.lakhina@gmail.com:
s/svn/WebDAV/g
The correct term to use here would be WebDAV over http (instead of svn over http). I suppose the reason for blocking would be that WebDAV is an extension of the http protocol. It adds certain methods like PROPFIND, COPY etc. So if your ISP blocks anything other than the basic HTTP methods (get,post, head,put,delete,options,trace) it will block WebDAV.
https is generally transparently proxied, so that should solve your problem.
on an unrelated note, i thought its not possible to transparently proxy HTTPS connections.
Anurag
On Wed, May 7, 2008 at 2:39 PM, Anurag anurag@gnuer.org wrote:
2008/5/7 Puneet Lakhina puneet.lakhina@gmail.com:
s/svn/WebDAV/g
The correct term to use here would be WebDAV over http (instead of svn
over
http). I suppose the reason for blocking would be that WebDAV is an extension of the http protocol. It adds certain methods like PROPFIND,
COPY
etc. So if your ISP blocks anything other than the basic HTTP methods (get,post, head,put,delete,options,trace) it will block WebDAV.
https is generally transparently proxied, so that should solve your
problem.
on an unrelated note, i thought its not possible to transparently proxy HTTPS connections.
Anurag
I meant transparent in the sense that since the proxy cant see your request content, it cant block based on the HTTP request method. Right?
-- http://web.gnuer.org/ -- http://mm.glug-bom.org/mailman/listinfo/linuxers
On 07-May-08, at 2:33 PM, Puneet Lakhina wrote:
works for me. Either your ISP is b0rked or some proxy is blocking svn over http. Some braindead sysadmins only allow svn over https
s/svn/WebDAV/g
what has WebDAV got to do with this??
The correct term to use here would be WebDAV over http (instead of svn over http). I suppose the reason for blocking would be that WebDAV is an extension of the http protocol. It adds certain methods like PROPFIND, COPY etc. So if your ISP blocks anything other than the basic HTTP methods (get,post, head,put,delete,options,trace) it will block WebDAV.
https is generally transparently proxied, so that should solve your problem.
how? the server is serving svn over http - so how can he use https?
On Wed, May 7, 2008 at 5:59 PM, Kenneth Gonsalves lawgon@au-kbc.org wrote:
On 07-May-08, at 2:33 PM, Puneet Lakhina wrote:
works for me. Either your ISP is b0rked or some proxy is blocking svn over http. Some braindead sysadmins only allow svn over https
s/svn/WebDAV/g
what has WebDAV got to do with this??
Almost everything. SVN uses WebDAV to access repositories over http.
http://subversion.tigris.org/webdav-usage.html http://svnbook.red-bean.com/en/1.1/ch06s04.html
The correct term to use here would be WebDAV over http (instead of svn over http). I suppose the reason for blocking would be that WebDAV is an extension of the http protocol. It adds certain methods like PROPFIND, COPY etc. So if your ISP blocks anything other than the basic HTTP methods (get,post, head,put,delete,options,trace) it will block WebDAV.
https is generally transparently proxied, so that should solve your problem.
how? the server is serving svn over http - so how can he use https?
Ofcourse here I assume that the server also supports https.
-- regards
Kenneth Gonsalves Associate, NRC-FOSS lawgon@au-kbc.org http://nrcfosshelpline.in/code/
On 07-May-08, at 6:04 PM, Puneet Lakhina wrote:
Almost everything. SVN uses WebDAV to access repositories over http.
http://subversion.tigris.org/webdav-usage.html http://svnbook.red-bean.com/en/1.1/ch06s04.html
ahh - learnt something new - thanks
The correct term to use here would be WebDAV over http (instead of svn over http). I suppose the reason for blocking would be that WebDAV is an extension of the http protocol. It adds certain methods like PROPFIND, COPY etc. So if your ISP blocks anything other than the basic HTTP methods (get,post, head,put,delete,options,trace) it will block WebDAV.
https is generally transparently proxied, so that should solve your problem.
how? the server is serving svn over http - so how can he use https?
Ofcourse here I assume that the server also supports https.
afaik most oss projects use http and dont support https
On Wed, May 7, 2008 at 6:37 PM, Kenneth Gonsalves lawgon@au-kbc.org wrote:
On 07-May-08, at 6:04 PM, Puneet Lakhina wrote:
Almost everything. SVN uses WebDAV to access repositories over http.
http://subversion.tigris.org/webdav-usage.html http://svnbook.red-bean.com/en/1.1/ch06s04.html
ahh - learnt something new - thanks
The correct term to use here would be WebDAV over http (instead of svn over http). I suppose the reason for blocking would be that WebDAV is an extension of the http protocol. It adds certain methods like PROPFIND, COPY etc. So if your ISP blocks anything other than the basic HTTP methods (get,post, head,put,delete,options,trace) it will block WebDAV.
https is generally transparently proxied, so that should solve your problem.
how? the server is serving svn over http - so how can he use https?
Ofcourse here I assume that the server also supports https.
afaik most oss projects use http and dont support https
I think the anonymous/guest checkout is over http, but the comitters have got to have https right? They have to send authentication information to the server and surely that doesn't travel over an unencrypted channel.
See here for an example of comitter access over https. http://www.apache.org/dev/version-control.html
-- regards
Kenneth Gonsalves Associate, NRC-FOSS lawgon@au-kbc.org http://nrcfosshelpline.in/code/
On 07-May-08, at 9:01 PM, Puneet Lakhina wrote:
afaik most oss projects use http and dont support https
I think the anonymous/guest checkout is over http, but the comitters have got to have https right? They have to send authentication information to the server and surely that doesn't travel over an unencrypted channel.
no. afaik sourceforge, berlios and google all use http for commits
On Thu, May 8, 2008 at 7:37 AM, Kenneth Gonsalves lawgon@au-kbc.org wrote:
On 07-May-08, at 9:01 PM, Puneet Lakhina wrote:
afaik most oss projects use http and dont support https
I think the anonymous/guest checkout is over http, but the comitters have got to have https right? They have to send authentication information to the server and surely that doesn't travel over an unencrypted channel.
no. afaik sourceforge, berlios and google all use http for commits
YES. YES. Read the FAQs.
See links for sourceforge and google.
http://code.google.com/support/bin/answer.py?answer=56665&topic=10386
http://alexandria.wiki.sourceforge.net/Subversion+-+Version+Control+for+Sour...
you dont use telnet to login to your remote systems right?
-- regards
Kenneth Gonsalves Associate, NRC-FOSS lawgon@au-kbc.org http://nrcfosshelpline.in/code/
On 08-May-08, at 11:52 AM, Puneet Lakhina wrote:
no. afaik sourceforge, berlios and google all use http for commits
YES. YES. Read the FAQs.
See links for sourceforge and google.
http://code.google.com/support/bin/answer.py?answer=56665&topic=10386
http://alexandria.wiki.sourceforge.net/Subversion+-+Version+Control +for+Source+Code
/me ducks and runs
-
Anurag -
Debarshi Ray -
Kenneth Gonsalves -
Puneet Lakhina -
Subhodip Biswas