Age | Commit message (Collapse) | Author |
|
|
|
I'm not including the preload file yet.
|
|
|
|
...not that there's any obvious justification for storing cookies for decades.
|
|
|
|
|
|
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.
|
|
BTW, is there a point in using a monospaced font?
Besides it looks like code printing (which is good),
a proportional-spaced font may be easier to read.
|
|
|
|
Although not allowed in text contexts, null characters should not
stop/halt/fail dpi protocol, thus the patch.
Test Example. Display a file with these contents:
null padding^@^@
(two trailing null characters)
and view source for it.
Note that dillo will not _display_ the file completely correct,
it will eat a char after each null, but this is not a problem in
dpi nor dpip but in rendering, the cache gets it right.
Adding code to correctly _display_ these anomalous pages is probably
not worth the effort though.
|
|
|
|
|
|
|
|
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...
|
|
|
|
|
|
|
|
I see that openbsd likes to complain when it's used, and we certainly
don't have a deep need for it in this case.
|
|
just specify https
|
|
|