Known problems/bugs in neon -*- text -*- --------------------------- * ne_lock_discover does not handle multiple (shared) locks on a single resource. * ne_version_pre_http11 gives inverse results to documentation. * SSL session caching issues; only cache for clean shutdowns, and only cache on shutdown, since the SSL_SESSION may change during an ne_session. * test failures in `socket' on some non-Linux platforms: 19. write_reset........... FAIL (write got 0 not reset) 20. read_reset............ FAIL (read got -3 not reset) * server auth should not run on a CONNECT request; once a connection has been CONNECT tunneled, subsequent requests through the tunnel should not give proxy auth. * what is passed as 'path' to req create hook: auth needs Request-URI; how does that interact with proxies? also they will be passed NULL for a CONNECT request, or "*" possibly as well. * XML API should not expose expat/libxml difference where attrs array may be NULL or non-NULL to startelm callbacks. * expect100 support is broken. * 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 (as it forces the SSL handshake to fail), but that would prevent opportunistic use of client certificates, of the "SSLVerifyClient optional" variety.
Generated by dwww version 1.11.3 on Tue Dec 10 21:49:44 CET 2013.