| Age | Commit message (Collapse) | Author |
|---|
|
algorithms
|
|
|
|
|
|
reported by Nick Warne http://lists.dillo.org/pipermail/dillo-dev/2016-July/010941.html
checking mbedtls/ssl.h usability... no
checking mbedtls/ssl.h presence... yes
configure: WARNING: mbedtls/ssl.h: present but cannot be compiled
configure: WARNING: mbedtls/ssl.h: check for missing prerequisite headers?
configure: WARNING: mbedtls/ssl.h: see the Autoconf documentation
configure: WARNING: mbedtls/ssl.h: section "Present But Cannot Be Compiled"
configure: WARNING: mbedtls/ssl.h: proceeding with the compiler's result checking for mbedtls/ssl.h... no
configure: WARNING: *** mbed TLS 2 not found. Disabling SSL/HTTPS/TLS support. ***
|
|
|
|
|
|
|
|
|
|
|
|
a status message
|
|
|
|
thread begins here:
http://lists.dillo.org/pipermail/dillo-dev/2016-February/010682.html
|
|
I never knew that if you give it a small string to copy into a big buffer,
it'll waste time filling the rest of it with '\0'.
|
|
|
|
|
|
|
|
|
|
I'm not including the preload file yet.
|
|
|
|
|
|
A site triggers this with a background image where the style is deleted
upon </div>, and Capi_stop_client() finds that a_Cache_client_get_if_unique()
is false, so nothing aborts the connection. And there's time for this to
happen because we're doing TLS handshake.
I don't know whether all of what triggered this is doing the right thing,
but at least when it comes to capi, we can see that there's the idea of
permitting it (with whether we ever actually want that in practice being
yet another question).
In any case, Http_make_query_str() definitely thinks the web is there.
If we really decided that we wanted connections to continue without webs,
we could stuff 1) what sort of thing are we requesting? 2) is this a
third-party request? into the socket data. Making the query earlier is
probably not advisable because we'd want the cookies available at the
time that we send the query and not the cookies that were available
somewhat earlier.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I used 'hg rename' and expected (at least hoped) that 'hg diff' would
do what I would naturally want, but no.
|
|
And separate http from https for safety while we're at it.
We were checking this where we needed to, but it would be easy to
forget about in the future. Not that very much happens when you
try http://example.com:443 or https://example.com:80, but I'm
being careful nevertheless.
|
|
openbsd tripped over this for me
|
|
titles)
I've noticed how users on forums can be like "Oh, it must be something about
bugs in dillo. But it manages to load the page". This is a degree of
misunderstanding which I wouldn't expect from anyone interested in using
dillo, but there it is, so I should deal with it.
|
|
I tried dillo on openbsd and, unsurprisingly, it seems fine with libressl.
I still would like it if some other TLS library would become the clear
choice for dillo at some point...
|
|
|
|
Just recently I added some mention of domainrc to the website. I hadn't
made enough of an effort to communicate the fact that it exists, and now
it's time to remedy that.
|
|
Normally I really like to make commits in small pieces that all compile
and make sense in isolation, but with this https work, the effort vs the
reward just wasn't going to make sense.
|
|
|
|
|
|
|
|
jeremy's valgrind logs have an instance of
==15610== Invalid read of size 4
==15610== at 0x8090B53: Http_socket_reuse (http.c:668)
|
|
|
|
|
|
|
|
|
|
|
|
|
