Note that expect100 is now sensible, and that ne_lock_refresh is not.

git-svn-id: http://svn.webdav.org/repos/projects/neon/trunk@332 61a7d7f5-40b7-0310-9c16-bb0ea8cb1845

1 files changed, 2 insertions, 4 deletions

diff --git a/BUGS b/BUGS
index 6bb69b1..f8e5d72 100644
--- a/BUGS
+++ b/BUGS
@@ -12,6 +12,8 @@ Known problems/bugs in neon                                      -*- text -*-
 * ne_lock_discover does not handle multiple (shared) locks on
   a single resource.
 
+* ne_lock_refresh does not update the passed-in lock structure.
+
 * SSL session caching issues; only cache for clean shutdowns, and
  only cache on shutdown, since the SSL_SESSION may change during
  an ne_session?
@@ -20,10 +22,6 @@ Known problems/bugs in neon                                      -*- text -*-
   how does that interact with proxies?  also they will be passed NULL
   for a CONNECT request, or "*" possibly as well.
 
-* expect100 support is broken: enable it per-request, don't bother
-caching support over the session, rely on the app only enabling it if
-it works.
-
 * It would be nice to fail with a friendly error message if a client
 cert is requested by the srever but one is not provided.  Currently,
 returning -1 from the provide_client_cert function would allow that