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/07/31 20:37:12 UTC
cause of svn update errors
OK, this was in fact the proxy server refusing http REPORT requests.
Happily, the proxy server is now being configured to handle them.
IMHO a user-level error message would be swell in this case, unless
there's no good way of telling that the cause is a restrictive proxy
server.
thanks,
hamilton
> % svn up
>
> ../svn/subversion/libsvn_ra_dav/util.c:332
> apr_error: #20014, src_err 0 : <Error string not specified yet>
> REPORT request failed on /repos/svn/trunk
>
> ../svn/subversion/libsvn_ra_dav/util.c:306
> apr_error: #20014, src_err 0 : <Error string not specified yet>
> The REPORT status was 400, but expected 200.
> %
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cause of svn update errors
Posted by Kieran <ki...@esperi.demon.co.uk>.
On Wed, 31 Jul 2002, Joe Orton wrote:
> On Wed, Jul 31, 2002 at 02:37:12PM -0600, Hamilton Link wrote:
> > OK, this was in fact the proxy server refusing http REPORT requests.
> > Happily, the proxy server is now being configured to handle them.
> >
> > IMHO a user-level error message would be swell in this case, unless
> > there's no good way of telling that the cause is a restrictive proxy
> > server.
>
> In general it could be useful to include the "reason phrase" in the
> error message, so it could say something like:
>
> "The REPORT status was 405 (Method Not Allowed), but expected 200."
>
> which might give a better idea of what the problem was. (In your case
> this wouldn't actually have helped, since the proxy gave out the wrong
> status code; a 403 or a 405 would have been correct, not a 400)
>
It might even be worth throwing out a HTTP TRACE message, as well.
Regards
Kieran
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cause of svn update errors
Posted by Joe Orton <jo...@manyfish.co.uk>.
On Wed, Jul 31, 2002 at 02:37:12PM -0600, Hamilton Link wrote:
> OK, this was in fact the proxy server refusing http REPORT requests.
> Happily, the proxy server is now being configured to handle them.
>
> IMHO a user-level error message would be swell in this case, unless
> there's no good way of telling that the cause is a restrictive proxy
> server.
In general it could be useful to include the "reason phrase" in the
error message, so it could say something like:
"The REPORT status was 405 (Method Not Allowed), but expected 200."
which might give a better idea of what the problem was. (In your case
this wouldn't actually have helped, since the proxy gave out the wrong
status code; a 403 or a 405 would have been correct, not a 400)
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org