AW: AW: AW: AW: Segmentation Fault with SVN Client related to serf

> -Ursprüngliche Nachricht- > Von: Philip Martin [mailto:philip.mar...@wandisco.com] > Gesendet: Donnerstag, 8. Januar 2015 14:34 > An: Viret Pierre, PF54 > Cc: users@subversion.apache.org > Betreff: Re: AW: AW: AW: Segmentation Fault with SVN Client related to serf > [...] > > I've nev

Re: svn forbidden error

It was actually a Location directive I. Apache. I had to do an Allow from IP address in that block in order to solve the problem. Thanks for you reply Tim Sent from my iPhone > On Jan 8, 2015, at 7:45 PM, Branko Čibej wrote: > >> On 08.01.2015 21:50, Tim Dunphy wrote: >> Hey all, >> >> I'v

Re: svn forbidden error

On 08.01.2015 21:50, Tim Dunphy wrote: > Hey all, > > I've configured subversion 1.8.10 from source with the serf > configuration option. > > Everything seemed to go smoothly. But when I try to do a checkout > from my repository I get this error: > > [root@aozmpwslp004la ~]# svn co http://$(hostn

svn forbidden error

Hey all, I've configured subversion 1.8.10 from source with the serf configuration option. Everything seemed to go smoothly. But when I try to do a checkout from my repository I get this error: [root@aozmpwslp004la ~]# svn co http://$(hostname -i)/svn/localmedia/applications/elections svn: E17

Re: mod_dav_svn.so does no more support lock functions

Thank you Dave, I have tried with the binaries compiled from Apache Haus and it works fine. I'm also using the mod_authnz_sspi.so extension from my friend Ennio. First I tried the 64bits binaries but it failed, said it was not a valid win32 application ! Finally I decided to use the 32bits binar

Re: AW: AW: AW: Segmentation Fault with SVN Client related to serf

Philip Martin writes: > I can't reproduce this against a standard server. I think I have worked it out. There was an error in my script: one of the XML response lines was missing a '\n' and this originally caused the client to report the HTTP response as too short, so I "fixed" it by added a tr

Re: AW: AW: AW: Segmentation Fault with SVN Client related to serf

Philip Martin writes: > I've converted your trace into a Python script to implement a server > that behaves like yours. I may have reproduced the problem. If I remove the 'Connection: close' headers and continue to force v1 I can get the client to crash using the dummy server. I suppose that m

RE: Authentication Questions

Thanks Philip, what you explained for the authz/authn caching makes sense. We recently performed a major upgrade of our IT infrastructure and I took the opportunity to upgrade our very old Subversion configuration (old physical server with Apache 2.2/SVN 1.4 to virtual server with 2.4/1.8). We h

RE: Roadmap update

> Any chance the Roadmap can be updated since Q2 2014 has come and gone?  > I'm sure there's been some functions completed, or nearly complete, > even if 1.9.0 is not ready for production. I would also be interested to know the status of the roadmap. David

Re: Authentication Questions

jt.mil...@l-3com.com writes: > I guess there's no caching of credentials since the path-based > authentication file can change at any time? I'm not clear what you mean by "caching of credentials". Subversion typically sends multiple HTTP requests over a single connection. Each HTTP request has

Re: AW: AW: AW: Segmentation Fault with SVN Client related to serf

writes: > The status line is not blocked. The debugging message means that we > have got an header with a null key and with the status line as value: > in this case the header is not added to the request sent back to the > client. This seems to be common that some HTTP Implementations return > su