Hi Madis, On Tue, 27 Jan 2004, Madis Janson wrote:
On Mon, 3 Nov 2003, Jorge Arellano Cid wrote:
On Sat, 25 Oct 2003, Madis Janson wrote:
Also, there seems to be one process for one connection, which makes hard to implement SSL session cache.
Yes, that happens with dpi filters. The idea in this case is to have an http dpi that's able to handle several connections at the same time (like the downloads dpi). That is: a dpi server instead of a dpi filter. With that scheme session cache is easy to implement.
(and BTW much easier for the developer because he can arrange things much more freely than when patching inside dillo).
content-type
(as above).
The https dpi would need to listen the HTTP stream and so has access to the content-type sent by the remote https server.
(http://article.gmane.org/gmane.comp.web.dillo.devel/1407)
if someone would create non-ssl dpi proxy plugin (that just makes http requests), i will add the ssl part to it (i have working ssl proxy code, which currently works using a patched dillo).
Interesting idea! I'll start working on it after the 0.8.0 release. Cheers Jorge.- PS : Dylan knows crypt stuff. You may work together on it. PS2: He's on dillo-dev.