Re: SSL in the browser

I had planned to wait until after 3.1 to integrate the ssl-in-browser
code, but since 1) dillo hasn't been moving toward release lately and
2) Johannes tells me that the patch has been working well for him, I
now plan to put it into dillo when I get a chance in coming days.

Having it in dillo means that dillo can be a better internet citizen
(http_max_conns, http_persistent_conns), there is certificate hostname
checking borrowed from wget, server name indication (fewer certificate
warnings), we can remember for the session that the user accepted the
use of a questionable certificate instead of continuing to give warnings,
we can check non-root-url certificates without endless warning popups...