You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Hamilton Link <he...@sandia.gov> on 2002/08/09 23:31:52 UTC

list of HTTP messages used by svn?

Is there a full list of the HTTP methods svn uses somewhere, that
someone could piont me to? From the documentation I can find (in
particular project_faq.html and INSTALL), the list of methods svn uses
include at least the following:

GET, PROPFIND, REPORT, OPTIONS, MERGE, MKACTIVITY, and CHECKOUT

But since the lists I can find are only partial lists and nowhere does
it suggest these are all the ones used, I'm reluctant to make any
assumptions.

If I had a complete list, I could go to the corp. proxy guy once instead
of many times, and reduce the risk of pissing him off and being left
with inadequate svn support in the proxy.

thanks,
hamilton


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn_client_status woes

Posted by Justin Erenkrantz <je...@apache.org>.
On Sat, Aug 10, 2002 at 03:03:48PM -0700, Brent R. Matzelle wrote:
> Here is the backtrace produced from gdb:
> 
> #0  0x40092190 in apr_palloc (pool=0x0, size=32) at apr_pools.c:613
> #1  0x400865cb in apr_hash_make (pool=0x0) at apr_hash.c:135
> #2  0x4003bb61 in svn_client_status (statushash=0xbfffebac, 
>     youngest=0xbfffebb0, path=0x81235ac "/home/brent/.bash_logout", 
>     auth_baton=0x8105d70, descend=0, get_all=1, update=0, pool=0x0)
>     at subversion/libsvn_client/status.c:151

apr_hash_make is getting passed with a NULL pool parameter.  That
is your culprit.  -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

svn_client_status woes

Posted by "Brent R. Matzelle" <bm...@yahoo.com>.
Hello Everyone,

I have been currently working on getting RapidSVN to look and
function equally on Linux/Unix as well as Windows.  However, I have
been getting segmentation faults in SvnFileStatus::retrieveStatus
when the svn_client_status() function is called.  

This works just fine under Windows but consistently bombs on Linux. 
Can someone take a gander at svn_file_status.cpp and let me know if
they see anything wrong?  You can quickly view it here: 

http://svn.collab.net/repos/svn/clients/rapidsvn/trunk/src/svn_file_status.cpp

Here is the backtrace produced from gdb:

#0  0x40092190 in apr_palloc (pool=0x0, size=32) at apr_pools.c:613
#1  0x400865cb in apr_hash_make (pool=0x0) at apr_hash.c:135
#2  0x4003bb61 in svn_client_status (statushash=0xbfffebac, 
    youngest=0xbfffebb0, path=0x81235ac "/home/brent/.bash_logout", 
    auth_baton=0x8105d70, descend=0, get_all=1, update=0, pool=0x0)
    at subversion/libsvn_client/status.c:151
#3  0x0805b311 in SvnFileStatus::retrieveStatus (this=0xbfffebe0, 
    path=@0xbfffec30, auth_baton=@0xbfffebe8) at
/usr/include/wx/string.h:457

Regards,

Brent.

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: list of HTTP messages used by svn?

Posted by Nuutti Kotivuori <na...@iki.fi>.
Hamilton Link wrote:
> Is there a full list of the HTTP methods svn uses somewhere, that
> someone could piont me to? From the documentation I can find (in
> particular project_faq.html and INSTALL), the list of methods svn
> uses include at least the following:
> 
> GET, PROPFIND, REPORT, OPTIONS, MERGE, MKACTIVITY, and CHECKOUT
> 
> But since the lists I can find are only partial lists and nowhere
> does it suggest these are all the ones used, I'm reluctant to make
> any assumptions.
> 
> If I had a complete list, I could go to the corp. proxy guy once
> instead of many times, and reduce the risk of pissing him off and
> being left with inadequate svn support in the proxy.

http://www.webdav.org/deltav/WWW10/deltav-intro.htm

A list copied from there:

HTTP/1.1: GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE, CONNECT

WebDAV: LOCK, UNLOCK, PROPFIND, PROPPATCH, COPY, MOVE, MKCOL

DeltaV: CHECKIN, CHECKOUT, UNCHECKOUT, VERSION-CONTROL, REPORT,
UPDATE, LABEL, MERGE, MKWORKSPACE, BASELINE-CONTROL, MKACTIVITY

Subversions uses no methods outside these. It doesn't use all of them
either, but it's better to support the full WebDAV/DeltaV than just
some arbitrary subset. If the proxy being configured is a recent
Squid, it probably has everything from HTTP/1.1 and WebDAV - and then
it only needs the DeltaV extensions added.

You can give that list to your corp. proxy guy and explain to him that
he can check the RFC's for further information.

-- Naked


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org