> From: Philip Martin
> Sent: Tuesday, 13 August 2013 19:59 PM
> Geoff Field <Geoff_Field_at_aapl.com.au> writes:
> >> -----Original Message-----
> >> From: Philip Martin
> >> Sent: Monday, 12 August 2013 18:57 PM Geoff Field writes:
> >> I can't reproduce that. Can you look in the apache log
> files to see
> >> the failed request? Can you reproduce the problem over http? Can
> >> you provide a network trace?
> > I have emailed Philip and Lieven directly with the network
> trace file
> > as it's a bit big (600-odd K) for a mailing list.
> It's an https trace so not much use to me.
That's a shame.
> > 10.63.36.64 - - [13/Aug/2013:10:51:13 +1000] "PROPPATCH
> > 97 HTTP/1.1" 401 580
> > 10.63.36.64 - AAPL\\gf [13/Aug/2013:10:51:13 +1000] "PROPPATCH
> > 97 HTTP/1.1" 207 475
> > 10.63.36.64 - - [13/Aug/2013:10:51:13 +1000] "CHECKOUT
> > /Subversion/Playground/!svn/ver/897/trunk HTTP/1.1" 401 580
> > 10.63.36.64 - AAPL\\gf [13/Aug/2013:10:51:13 +1000] "CHECKOUT
> > /Subversion/Playground/!svn/ver/897/trunk HTTP/1.1" 201 439
> > 10.63.36.64 - - [13/Aug/2013:10:51:13 +1000] "HEAD
> > /Subversion/Playground/trunk/test4.txt HTTP/1.1" 401 -
> When I try to reproduce the problem I get a HEAD request that
> "404 not found" rather than "401 unauthorized". What sort of
> authentication have you configured? Are you using path-based authz?
Here's what I think is the relevant section of our httpd.conf:
AuthName "Subversion repositories"
# SSPIUsernameCase lower ## Breaks authentication
# SSPIPerRequestAuth Off ## This breaks Apache2
Note that we're running Apache 2.0. Here are the exact details from the server's "Services" applet:
Apache/2.0.54 (Win32) DAV/2
I'm trying (as a background task from my regular job) to upgrade to Apache 2.2, but it's proving to be a bit of a learning experience.
Part of our issue is that the people who originally set it all up (and who started doing the upgrade once upon a time) have moved on to other jobs. Another part is that maintenance of SVN is a very small part of my job - so small it's under "other duties as directed" in the position description, along with numerous other tasks. (I guess many of us on this mailing list will be in similar positions, too.)
I'm still learning, even 25+ years into my work life...
Thanks for your patience.
- The contents of this email, and any attachments, are strictly private
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files.
Received on 2013-08-14 01:02:49 CEST