Ben's got this for 0.34.

See this thread, in which Ben Collins-Sussman describes the diagnosis and asks
for help, followed by responses from Greg Hudson and Justin Erenkrantz:

http://subversion.tigris.org/servlets/BrowseList?list=dev&by=thread&from=135712

Based on the above, Fitz and I are going to see if it's a quick hack to just
make our mod_dav_svn authz_read() callback just handle digest auth specially
right now.  The "right" solution, as Justin says, would be to fix
mod_auth_digest, but we can't wait for another Apache release anyway, so it
needs to work with the current  mod_auth_digest.

If this turns out not to be a quick fix, then we'll just have to live without
digest auth.  I know that sucks, but we can *not* afford to roll back the
checkout/update performance improvements (which necessitated authz_read and its
subrequests) just to support digest auth again.

Dang it, why didn't the reassignment take?  Assigning to me, again.

The right place to fix this is in mod_auth_digest in httpd, as Justin Erenkrantz
and others have pointed out.  We should close this issue when a corresponding
issue is opened in the Apache issues database; in the meantime, moving to the
"no milestone" milestone, as there is no code change to Subversion here.

Apache HTTPD Server issue filed:

   http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25040

I think the best thing to do is close this issue now... Closing.

Well, the FIXED resolution is wrong.  Sigh; not going to bother to reopen just
to close as INVALID or whatever, but I hope someone reads this comment if
they're reading the issue at all :-).

Note that http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25040 now has the
"PatchAvailable" keyword.

Closing this issue as INVALID.  Will add a FAQ item about digest auth.

FAQ item committed in r8386.

Closing issues marked as "invalid"

Closing issues marked as "invalid"