Typical console error mesage (from yahoo mail secure logon page)
lookes like: |-----------------
Nav_open_url: Url=>https://login.yahoo.com/config/login?.branch=&.src=ym&.v=0&.u=bh9jje50 fau8u&.last=&promo=&.intl=us&.bypass=&.partner=&pkg=&stepid=&.done=< url_str = https://login.yahoo.com/config/login?.branch=&.src=ym&.v=0&.u=bh9jje50fau8u &.last=&promo=&.intl=us&.bypass=&.partner=&pkg=&stepid=&.done= main.c:153: get_command: dpid tag is NULL
: main.c:326: main: get_command failed : {In https.filter.dpi}
SSL_connect failed Dpi: [Dpi_process_io] IOClose
|-----------------
and dillo provides no other feedback. Since I usually involk dillo from my window manager, the console output is not normally availible to me.
I will take a look at it as soon as a I get a chance.
Perhaps returning a SSL connection failed page would be nice.
I'll see what I can do. I'm worried about code bloat, esp since Dillo prides itself on being very small.
Dumb question: Is http 1.1 authentication amenable to a similar treatment? That is one of the features I really miss.
http 1.1 *anything* would require Dillo to support HTTP 1.1 When workingo n the HTTPS plugin, all of the requests that I pass through are HTTP 1.0 messages, meaning that we are indicating, at least to the other server, that we don't support any HTTP 1.1 features. Actually, all the HTTPS filter DPI does is open up an SSL connection to the remote computer and then pass all the HTTP connections through. THe only thing that makes it complicated at all is dealing with certificate isssues if they are invalid. - Garrett Kajmowicz