January 2005 - Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]dillo-0.8.4-rc1

by Livio Soares

Hey, Patrick Shanahan writes: > * Jorge Arellano Cid <jcid(a)dillo.org> [01-06-05 20:09]: > > On Thu, Jan 06, 2005 at 03:38:33PM -0500, Patrick Shanahan wrote: [...] > > But there is no src/https.c within the rc1 tar file ???? Typo. Should read dpi/https.c (look for the ENABLE_SSL #undef). Good luck, Livio

Jan. 7, 2005

Re: [Dillo-dev]dillo-0.8.4-rc1

by Patrick Shanahan

* Jorge Arellano Cid <jcid(a)dillo.org> [01-06-05 20:09]: > On Thu, Jan 06, 2005 at 03:38:33PM -0500, Patrick Shanahan wrote: > > * Jorge Arellano Cid <jcid(a)dillo.org> [01-06-05 14:46]: > > > I just finished packing the tarball for dillo-0.8.4-rc1. > > ... > > > Please grab it ASAP, test it throughly and report your findings > > > (finding no problems is a good sign ;). Some emphasis should be > > > put on the newest file server dpi and on compiling on 64 bit > > > machines. > > > > ?? and the URL ?? > > Forgoten somewhere inside my weary mind... :-) > > http://www.dillo.org/download/dillo-0.8.4-rc1.tar.bz2 A build on SuSE 9.0 is available at: http://wahoo.no-ip.org/~pat/dillo-0.8.4-rc1.i686.rpm I am playing with the rc1 now and have opened Yahoo, but cannot log in: Hi! This is the https dpi that just got a request to send the following HTTP query: { POST /config/login?4ghd98ggqpem2 HTTP/1.0 Host: login.yahoo.com User-Agent: Dillo/0.8.4-rc1 Cookie2: $Version="1" Content-type: application/x-www-form-urlencoded Content-length: 288 .done=http%3A%2F%2Fmy.yahoo.com%2Fp%2Fd.html&.tries=1&.src=my&.md5=&.hash=&.js=&.last=&promo=&.intl=us&.bypass=&.partner=&.u=4ks2nvl0ts3sp&.v=0&.challenge=60tz46k8k12hkA3xCJ3iKrQaajYW&.yplus=&.emailCode=&pkg=&stepid=&.ev=&.branch=&hasMsgr=0&.chkP=Y&login=os2pat&passwd=br549&.save=Sign+In } *** Dillo's prototype plugin for https support is disabled now *** If you want to test this alpha support code, just remove line 56 from https.c, recompile and reinstall. (beware that this https support is very limited now) .... But there is no src/https.c within the rc1 tar file ???? otherwise, appears solid. Will report more findings after further usage. thanks, -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

Jan. 7, 2005

Re: [Dillo-dev]dillo-0.8.4-rc1

by Jorge Arellano Cid

On Thu, Jan 06, 2005 at 03:38:33PM -0500, Patrick Shanahan wrote: > * Jorge Arellano Cid <jcid(a)dillo.org> [01-06-05 14:46]: > > I just finished packing the tarball for dillo-0.8.4-rc1. > ... > > Please grab it ASAP, test it throughly and report your findings > > (finding no problems is a good sign ;). Some emphasis should be > > put on the newest file server dpi and on compiling on 64 bit > > machines. > > ?? and the URL ?? Forgoten somewhere inside my weary mind... :-) http://www.dillo.org/download/dillo-0.8.4-rc1.tar.bz2 -- Cheers Jorge.-

Jan. 7, 2005

Re: [Dillo-dev]dillo-0.8.4-rc1

by Patrick Shanahan

* Jorge Arellano Cid <jcid(a)dillo.org> [01-06-05 14:46]: > I just finished packing the tarball for dillo-0.8.4-rc1. ... > Please grab it ASAP, test it throughly and report your findings > (finding no problems is a good sign ;). Some emphasis should be > put on the newest file server dpi and on compiling on 64 bit > machines. ?? and the URL ?? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

Jan. 6, 2005

[Dillo-dev]dillo-0.8.4-rc1

by Jorge Arellano Cid

Hi, I just finished packing the tarball for dillo-0.8.4-rc1. Please excuse me for the delay, but I received a security notice that needed to be addressed (CAN-2005-0012), and I discovered a minor bug with the HEAD tag implicit-close handling code. All of this is fixed in the tarball now, plus a few comments. Please grab it ASAP, test it throughly and report your findings (finding no problems is a good sign ;). Some emphasis should be put on the newest file server dpi and on compiling on 64 bit machines. Enjoy! -- Cheers Jorge.-

Jan. 6, 2005

Re: [Dillo-dev]cache replace

by Thorben Thuermer

On Thu, 6 Jan 2005 21:18:17 +0800 "Yu Zenghui" <yuzenghui(a)people.com.cn> wrote: > hello all: > it seems that dillo doesn't use cache replace algorithms. it simply > inserts new entry into the hash table. > then if the program runs for a long time, it will use more and more memories. > doesn't it? exactly. there's a patch that i've been using for years, it's perfectly stable (but i'm not sure if it applies cleanly to current versions): http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-January/000073.html - Thorben

Jan. 6, 2005

[Dillo-dev]cache replace

by Yu Zenghui

hello all: it seems that dillo doesn't use cache replace algorithms. it simply inserts new entry into the hash table. then if the program runs for a long time, it will use more and more memories. doesn't it?

Jan. 6, 2005

[Dillo-dev]Re: dillo patch: entities (BUG#605)

by Jorge Arellano Cid

On Tue, Jan 04, 2005 at 01:33:01PM +0100, Matthias Franz wrote: > Hi Jorge, > > On Mon, Jan 03, 2005 at 12:05:59PM -0300, Jorge Arellano Cid wrote: > > I just reviewed and commited the patch. > > Great! > > > > > * The ';' at the end is no longer required. In fact, it is optional > > > according to the SGML spec (see also Sec. 5.3 of the HTML 4.01 spec). > > > Omitting the ';' produces a warning. > > > > When show_extra_warnings is set. > > > > I wonder if it is better to always rise the warning. Of course > > it is perfectly legal for SGML but IIRC XHTML requires the ';' > > and authors prefer to add it with a view to avoid problems, so a > > reminder should be welcome. e.g. www.linuxpackages.net. > > That depends on what the (extra) warnings are intended for. I thought > that ordinary HTML_MSG are for errors, so that (ideally - we/you don't > want to be 100% perfect) if show_extra_warnings is off, "no errors" means > that the page is valid HTML. If show_extra_warnings is on, then one gets > additonal warnings, for example about bad style, incompatibility with > XHTML etc. Of course, this is a design question. I also agree with this view. It provides a simple formal definition too ;). Let's keep it now and see what happens. > One more remark about the HTML error messages. I would suggest the > following: > > * Leave out the "HTML warning" at the beginning of each entry - all the > more that most entries are errors. > > * Introduce a macro HTML_ERROR for real error messages. It replaces > HTML_MSG (in most of the source code; internally it may call HTML_MSG). > > * Introduce a macro HTML_WARNING like > > #define HTML_WARNING(fmt...) if (prefs.show_extra_warnings) \ > HTML_MSG("warning: " ## fmt) > > (not tested - you get the idea). > > What do you think about it? It looks like a good idea. It's more correct to label them "HTML error" and "HTML warning" than as it is done currently. My main concern is about page authors taking it personal. ;-) The other point is that we'd have to be very accurate. The nesting detection is ok now, but we'd have to start taking into account whether we're dealing with HTML.(version) or XHTML for some messages. > > > I made a minor change to avoid the #ifdefs. > > good idea > > > > Ah, we're now raising a warning when a named entity is not > > found. I don't know whether our list is complete. It'd be good to > > check because we could be giving misleading warnings for a small > > yet unsupported set. > > OK, I'll do it. But give me some days ... -- Cheers Jorge.-

Jan. 5, 2005

[Dillo-dev]Re: styles leak bug

by Jorge Arellano Cid

Hi Roberto, On Sun, Jan 02, 2005 at 01:28:07PM -0500, Roberto Sanchez wrote: > Jorge Arellano Cid wrote: > >=== > > > > Have you had the time to look into the styles leak bug? > > > > Only briefly. I also noticed that it occured on another webpage that > I developing for my church. I will let you know as soon I can figure > something out. Good news: I had some luck with an idea to test the origin of it. It's fixed in the CVS now! I'll try to pack the rc1 tarball tomorrow. -- Cheers Jorge.-

Jan. 4, 2005

Re: [Dillo-dev]2005

by Jeremy Henty

Jorge Arellano Cid wrote: > ... this is mainly a bugfix release and it has proven very > stable as from CVS. Seconded! I pulled down the CVS a few days ago to see if I could generate any bug reports before the -rc1, but it's been rock-solid! Here's to Dillo in 2005! Jeremy Henty

Jan. 4, 2005