
Known problems/bugs in neon                                      -*- text -*-
---------------------------

* SSL fails on platforms without a /dev/random. Need a mini-PRNG, or
  just require EGD where necessary.

* redirect code should escape Location URL before calling 
  ne_set_request_uri.

* fix the FIXME in ne_pull_request_body

* if connection is aborted while reading a chunked response body,
  ne_end_request will still attempt to read from the trailing headers?
  (not verified)

* when name resolution returns >1 IP address, should cycle through
  addresses if first one fails.

* SSL shutdown problems when using non-persistent connections? seems
to be a messy problem; any way to avoid the RST? Probably it's just an
inherent race between server&client sending the SSL closure alert.

2 11 0.2233 (0.0050)  C>S  application_data
2 12 0.2572 (0.0338)  C>S  application_data
2 13 0.2781 (0.0209)  S>C  application_data
2 14 0.2784 (0.0002)  S>C  Alert
2    0.2785 (0.0000)  S>C  TCP FIN
2 15 0.2827 (0.0042)  C>S  Alert
2    0.2853 (0.0025)  C>S  TCP RST
