| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
The handshake stuff should be named handshake. What should you call
initialize/setup plus handshake, then? I don't know, but 'connect'
for now, anyway.
|
|
as mentioned in the previous commit msg
|
|
Johannes reported that mbed TLS didn't like the connect() to be ongoing
still when the tls handshake was started on osx or dragonfly.
For an earlier version of the fix (which failed), it was basically free
to iterate through the IP address list upon connect() failure, so that
was implemented, and now I'm artificially breaking this patch into two
pieces to commit that separately.
|
|
|
|
You can trust an intermediate certificate in a chain, so let's be careful
with words here. It would of course be better to tell the user which
certificate was trusted in that case, but my understanding is that I would
have to go through each certificate in the chain and try to match it against
all of the trusted certificates, like mbed tls's verification code does in
the first place. This would involve a lot of digging around in mbed tls's
structures and using resources...
|
|
Until late 2007, it set a variable showing that ipv6 was working.
|
|
|
|
|
|
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. ***
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Avoid closing the <A> element until HTML5 rules are in place for the parser.
|
|
No longer necessary since the new nesting-cleanup design.
|
|
No longer necessary after the redesign of the parser's cleanup
process for tag nesting.
|
|
This needed moving around some functions, nothing else.
FWIW, we had it declared extern because that's C++ way to declare a forward
variable, the side effect of it being extern linkage.
|
|
* Forbidden nesting now is handled by cleanup_at_open.
(it previously used an ad-hoc function hooked into the process)
Much safer and versatile now. [1],[2],[4]
* Heuristical cleanup at close is no longer used.
cleanup_at_close is now based on block/inline element/container semantics,
and also cosiders special nesting rules expressed in the DTD for HTML-4.01.
Note: this design is easy to tailor for HTML5. [2]
* Bug reporting changed and is now is more centralized in cleanup_to_idx.
* The bug meter gives more accurate and concise messages. [4]
* Page rendering improved as now the cleanup process strives to produce
a correct tree out of Tag Soup, before feeding it to Dw. [4]
* Better handling/recovery from Tag Soup (even in the worst cases). [5]
* The w3c_plus_heuristics=FALSE mode was removed (not necessary anymore)
* Elements with optional close also follow Firefox de facto rules.
* Special case logic is now isolated in helper functions.
A few examples:
[1] http://dillo.org/test/cross-nesting-simple.html
[2] http://slashdot.org/
[3] http://apod.nasa.gov/apod/ap160604.html
[4] http://www.mypetchicken.com:80/catalog/Day-Old-Baby-Chicks/Olive-Eggers-p1478.aspx
[5] http://dillo.org/test/sd3.html
|
|
It was redundant with the "inline element" flag. i.e.
"block element" = ~"inline element"
|
|
|
|
|
|
|
|
|
|
|
|
This is the cleanup at open time (the other patch is the cleanup
at close time); they catch different problems.
e.g. <a href="1.html">Word1 <a href="2.html">Word2</a>
Fixes http://apod.nasa.gov/apod/ap160604.html
|
|
|
|
|
|
|
|
This avoids false-positive nesting messages from the bug meter.
|
|
A lingering open A element can lead to invisible content.
e.g. http://slashdot.org/
Note: slashdot_a_bug.html testcase in my HD.
|
|
|
|
|
|
BODY and HTML have optional open and close, making them tricky to handle.
Even more when considering Tag soup pages with multiple body or html
sections, and corner cases.
This patch tackles the problems by leaving the first HTML and BODY
stack elements open, until EOF.
There's also better html-bug detection and messages, and more accurate
comments in the code.
Beware: it may look simple, but it's not!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
