- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]pthreads
by Jorge Arellano Cid Nov. 24, 2004

Nov. 24, 2004

On Wed, Nov 24, 2004 at 03:15:15PM +0100, Riccardo Mottola wrote: > Hey Jorge, > > just a quick answer, but I am ina hurry > > > I have solaris, I have gcc. so I can test and compile. I have also > MkLinux which is linux where threads are mapped to mach threads (linux > on mach microkernel). > > > What source code should I run? How do i check for memory leaks (no > valgrind for solaris)... I posted it to the mailing list with instructions. You can find it here: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-November/002436.html The mail thread starts at: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-November/002429.html BTW, I'm making some tests in dillo using the results explained there, and the results are impressive: For instance: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jcid 3234 2.5 13.9 663804 13116 pts/15 S+ 11:59 0:05 ./dillo jcid 3238 0.0 13.9 663804 13116 pts/15 S+ 11:59 0:00 ./dillo (see the huge virtual size? It's a simple page with lots of tiny images). The same dillo, this time using the explicit detached-attribute pthread creation technique, gives: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND jcid 3792 11.8 11.0 14116 10448 pts/15 S+ 12:49 0:07 ./dillo jcid 3793 0.3 11.0 14116 10448 pts/15 S+ 12:49 0:00 ./dillo Same code, same page. Something really weird is going on here! Does anyone know the email of the pthreads library maintainer? -- Cheers Jorge.-

1 0

[Dillo-dev]Parser orthogonalization
by Jorge Arellano Cid Nov. 21, 2004

Nov. 21, 2004

Hi there, A few days ago I finished the: [1] Orthogonalize the parser (leaks, XML, CSS) task from the list. I didn't commit it inmediately because of the pthreads issue we're still workint in (it showed as a parser bug when in fact it was elsewhere). Now the large parser patch is commited (a 70KB beast!). From the ChangeLog: <q> * Orthogonalized the generic parser: - Fixes memory leaks and widget state when recovering from bad HTML. - Improves error detection and validation (needed by XHTML). - Makes DOC tree generation possible (needed by CSS). - Cleaner design of handling routines for bad HTML. - Orthodox treatment of double optional elements (HTML, HEAD, BODY). - Lots of minor code cleanups. </q> That's the summary. Now tags are always pushed into the stack when they're found and the respective closing functions are always called when finishing them, no matter if this is triggered by an explicit tag, optional close, or bad-HTML cleanup. This is very important because of the above explained reasons. The routines for handling HTML cleanup (optional, magic and bad HTML) were mostly isolated into three functions: Html_test_section() Html_stack_cleanup_at_open() Html_tag_cleanup_at_close() (fairly commented in the source). In brief: the good news of all of this patch is that it makes much easier to understand, improve and maintain the parser (eventually to chop, merge or reuse too), fixes memory handling, widget creation state, validation, and is also good for future CSS, XHTML. For instance, look at the new <P> and </P> tag treatment at: http://www-106.ibm.com/developerworks/eserver/articles/framework.html Now, I'm back to pthreads, ah, and I have more cleanups already done waiting for commit, some patches pending, the usual stuff! -- Cheers Jorge.-

1 0

[Dillo-dev]Dillo and multimedia keys
by Andrea Spadaccini Nov. 20, 2004

Nov. 20, 2004

Hi everyone, does Dillo support "strange" keys that are configured with Xmodmap? I'd like to hit the "back" button (XF86Back) and go back one page, and so on... If Dillo doesn't support this, you could give me suggestions on how to implement it. I know a little C, and maybe I could be able to help you. Thanks in advance -- [ Andrea Spadaccini a.k.a. Lupino / Lupin85 - from Catania ] [ MAIL: lupin85(at)email.it - ICQ: 91528290 - Linux 2.4.22 ] [ Linux Registered User #313388 - Powered by Slackware 9.1 ] -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Email.it Phone Card: chiami in tutto il mondo a tariffe imbattibili da tutti i telefoni fissi e cellulari! Clicca e scopri come Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2686&d=20-11

1 0

[Dillo-dev]dns error with static dillo
by Roberto A. Foglietta Nov. 16, 2004

Nov. 16, 2004

Hi, please try to reproduce this bug: I've compiled dillo with -static in linking but 0.8.2 --> 0.8.4rc1 show the same problem: dns error! [roberto@wsraf src]$ ./dillo Gdk-WARNING **: locale not supported by C library GLib-WARNING **: getpwuid_r(): failed due to: No such user 1309. Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data Gtk-WARNING **: libc.so.6: cannot handle TLS data dillo_dns_init: Here we go! Disabling cookies. Nav_open_url: Url=>about:splash< Nav_open_url: Url=>http://www.lugge.net< Dns_server [0]: www.lugge.net is (nil) Dillo: normal exit! -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

2 1

[Dillo-dev]refresh tag patch for 0.8.4 (and fix)
by Roberto A. Foglietta Nov. 16, 2004

Nov. 16, 2004

Hi, previous patch was little buggy, I hope this is better and it's against the last version I know. I hope you will interested in apply it. :-) Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

1 0

[Dillo-dev]https by lynx -source
by Hanspeter Roth Nov. 15, 2004

Nov. 15, 2004

Hello, I don't know where to post feature requests. So I try here. Could one do a preliminary implementation of HTTPS (SSL) via piping to `lynx -source %s'? -Hanspeter

1 0

[Dillo-dev]Toolkit & dillo
by Lars Segerlund Nov. 15, 2004

Nov. 15, 2004

There has been a lot of talk about toolkits and dillo, and I had a small idea. What about using lesstif ( Motif ) for dillo ? It's fairly small ( you can bring only the widgets you need ) and if done with some care a statically linked dillo would not be bloated. I can have a look at it, but I would like the general opinion first, ( I would even give Xt a shot :-) that way it would be FAST & SMALL ). regards, Lars Segerlund.

4 7

[Dillo-dev]Orthogonalize the parser (leaks, XML, CSS)
by Jorge Arellano Cid Nov. 15, 2004

Nov. 15, 2004

Hi there, I'm devoted 100% to this task now. It started as a small polish and ended being a huge patch. It's incredible how tricky optional tags can get when combined into a pot of tag soup! :-) Add, memory management (almost done), validation, HTML+XML soup and you'll get the idea. I'm testing now. It seems pretty good by now, but there's a page where it hangs dillo with almost no CPU consumption. A riddle to solve... -- Cheers Jorge.-

1 0

Re: [Dillo-dev]Task list & priorities
by Jorge Arellano Cid Nov. 9, 2004

Nov. 9, 2004

Hi Brian, Please keep this thread on dillo-dev. On Tue, Nov 09, 2004 at 08:12:50AM -0500, Brian Hechinger wrote: > On Mon, Nov 08, 2004 at 06:15:59PM -0300, Jorge Arellano Cid wrote: > > > > Great! > > Now we have a man in charge of it. > > i would be honored. > > > str = a_Prefs_get("font_factor"); > > if (str) > > ff = strtol(str); > > g_free(str); > > i've read all your email, and it looks like mostly enough to get me started, > but i just had this thought: > > if the dpi reads all the rc files in, we're going to have to be able to > specify which rc file we want to get our config from. we need to > implement a system of scope for the rc files. i don't want the cookie > module asking if it has permission to authorize a site to use cookies > by getting it's config from the cacherc which has an identical format. > > what do you think is the best way to go about doing that? make the rc > filename a requirement in the call? > > str = a_Prefs_get("font_factor", "dillorc"); This is a good idea to start with. > > and then in the dpi just have the rc files as a linked list with an entry for > the filename to do a strcmp() on? Maybe, but remember that cookiesrc has another format. It's not a variable/value pairs list, but a list of instances of the same abstract variable (to name it somehow ;). This also needs some thought. > > also, i still need to read about dpis of course, but are they long running > processes? Dpi servers, YES. Dpi filters come and go per request. > the way i'm thinking is that we don't want the rc files read > every time a preference is needed, so the first instance of dillo will start > the config dpi running, and it will continue to run until there are no more > instances of dillo running. does this sound reasonable? Yes. In fact, that's what the bookmarks dpi server does. You don't even have to worry about launching a dpi, that's the dpid job. It's done automatically. -- Cheers Jorge.-

1 0

[Dillo-dev]Task list & priorities
by Jorge Arellano Cid Nov. 8, 2004

Nov. 8, 2004

Hi there, Here I'm attaching the draft for the priorities list we're working on with Sebastian. Note that [1] Parsing of XML empty tags (e.g <script/> as <script></script>). is already done! and I'm working on the parser to avoid memory leaks with bad HTML, to be able to get the doc tree from parsing (XML well formedness validation and hopefully good for CSS too). Let's name this one as: [1] Orthogonalize the parser (leaks, XML, CSS) And here are a few to add to the list too: [ ] Login messages for the ftp dpi. [ ] Bookmarks dpi "sort" function. [ ] Back/Forward for #anchored links. -- Cheers Jorge.- PS: Please conside all of these works when I'm sending delayed answers :-P

2 2

[Dillo-dev]Parsing of XML empty tags (e.g <script/> as <script></script>).
by Jorge Arellano Cid Nov. 6, 2004

Nov. 6, 2004

Hi there, Well, the priorities list draft had this one with top priority (among others): <q> [1] Parsing of XML empty tags (e.g <script/> as <script></script>). </q> I'll post the priorities draft tomorrow for you to read, probably before Sebastian has a chance to review it... Unto the bug, it's BUG#514 and seems also #587. It needs some testing. Thorben: Do you have a test page for #587? --- Topic change (cache control): Brian: Take a look at BUG#161, Madis worked on the same problem long ago. Some ideas may be saved... I'm not saying the patch is wrong, I just happened to notice this entry while skimming. -- Cheers Jorge.-

3 4

[Dillo-dev]dpi menu and inteface hadling question
by Diego Sáenz Nov. 4, 2004

Nov. 4, 2004

I have made some proof of concept about dpi menu handling with a patch that add a dpi command that add a toolbar item/button and some test commands. ¿must i continue with menus or must i wait for fltk port and universal ccc implementation? The attached files are the b2ziped patch and a b2ziped and tared directory tree with some test files. Look at the second attachment for the dpi command. To test use the patch (works from cvs 2004-09-18 to current cvs), uncompres the directory in a /home/SOME_USER/.dillo/dpi/ directory, run the patched dillo and put dpi:/dpitest/ in the location bar. Then you can use the buttons that apear in the toolbar. Please if you have any suggestion reply and say it. I am open to change even command name :) If dillo suported onevent and css or javascript all the dillo interface could be a html page with an iframe(or something like that) that contain the site viewed. An external dpi or program could modify the interface page to add buttons or menu items when dpis ask for it and say to dillo to refresh interface page. I think this is the way that less code add to dillo but it is imposible for now and waste a few mem. DarkSpirit/Diego Saenz PD: sorry for my english

1 0

[Dillo-dev]Memory leak bug
by Roberto A. Foglietta Nov. 3, 2004

Nov. 3, 2004

Hi, I didn't find memory leak bug but I have to say this: waiting html page load complete doesn't help. I have done a patch which after first load doesn't show images BUT I lost it because I didn't care it... But when I saw my logs I see that patch fixed memory leak. Even if memory leak has nothing to do with images because trivial pages has no images. Probably 4kb is a structure not data. Thinking memory leak is generated by losing a structure instead data could explain why has fixed size (4kb for each reload) and probably why it happen only during a reload. In reload some data is cached but structures a created and destroyed... probably not all of them. Unfortunately it's time I have to find another browser to use it in my project. Sorry. Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

2 2

[Dillo-dev]protocol handler dpi for mailto:, etc.
by Lee Bigelow Nov. 1, 2004

Nov. 1, 2004

Hello again, I did up a proto-type bash shell dpi for handling unsupported protocols, like mailto:, with external applications. I called it xproto. It uses the config file $HOME/dillo/protorc to decide what to do. The plugin will make a default one you can edit when it's first run. I'm working on the C version, but I'm just learning C, so it'll take me a bit. One thing I can't seem to figure out is how to send a url from the plugin to dillo and have dillo display that page. For example I would like the url gg:water to send dillo http://www.google.com/search?q=water For now I just have it open up another dillo. I tried sending <dpi cmd="open_url" url="http://www.google.com/search?q=water"> but that didn't work, booo. Again, xproto.filter.dpi is just a shell script, so play away. If you have any hints on the gg: thing let me know, please... The patch, against dillo-0.8.2: -------------------------------------- diff -pruN dillo-0.8.2/dpi/Makefile.am dillo-0.8.2-xproto/dpi/Makefile.am --- dillo-0.8.2/dpi/Makefile.am 2004-01-29 17:04:05.000000000 -0330 +++ dillo-0.8.2-xproto/dpi/Makefile.am 2004-10-31 09:51:39.000000000 -0330 @@ -5,11 +5,13 @@ downloadsdir = $(libdir)/dillo/dpi/downl ftpdir = $(libdir)/dillo/dpi/ftp httpsdir = $(libdir)/dillo/dpi/https hellodir = $(libdir)/dillo/dpi/hello +xprotodir = $(libdir)/dillo/dpi/xproto bookmarks_PROGRAMS = bookmarks.dpi downloads_PROGRAMS = downloads.dpi ftp_PROGRAMS = ftp.filter.dpi https_PROGRAMS = https.filter.dpi hello_PROGRAMS = hello.filter.dpi +xproto_PROGRAMS = xproto.filter.dpi bookmarks_dpi_LDADD = @GLIB_LIBS@ downloads_dpi_LDADD = @GLIB_LIBS@ diff -pruN dillo-0.8.2/dpi/Makefile.in dillo-0.8.2-xproto/dpi/Makefile.in --- dillo-0.8.2/dpi/Makefile.in 2004-07-06 14:31:24.000000000 -0230 +++ dillo-0.8.2-xproto/dpi/Makefile.in 2004-10-31 10:18:28.000000000 -0330 @@ -44,6 +44,7 @@ downloads_PROGRAMS = downloads.dpi$(EXEE ftp_PROGRAMS = ftp.filter.dpi$(EXEEXT) https_PROGRAMS = https.filter.dpi$(EXEEXT) hello_PROGRAMS = hello.filter.dpi$(EXEEXT) +xproto_PROGRAMS = xproto.filter.dpi$(EXEEXT) subdir = dpi DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 @@ -53,14 +54,15 @@ am__configure_deps = $(am__aclocal_m4_de mkinstalldirs = $(mkdir_p) CONFIG_HEADER = $(top_builddir)/config.h CONFIG_CLEAN_FILES = -am__installdirs = "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)" +am__installdirs = "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(xprotodir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)" bookmarksPROGRAMS_INSTALL = $(INSTALL_PROGRAM) downloadsPROGRAMS_INSTALL = $(INSTALL_PROGRAM) ftpPROGRAMS_INSTALL = $(INSTALL_PROGRAM) helloPROGRAMS_INSTALL = $(INSTALL_PROGRAM) +xprotoPROGRAMS_INSTALL = $(INSTALL_PROGRAM) httpsPROGRAMS_INSTALL = $(INSTALL_PROGRAM) PROGRAMS = $(bookmarks_PROGRAMS) $(downloads_PROGRAMS) $(ftp_PROGRAMS) \ - $(hello_PROGRAMS) $(https_PROGRAMS) + $(xproto_PROGRAMS) $(hello_PROGRAMS) $(https_PROGRAMS) am_bookmarks_dpi_OBJECTS = bookmarks.$(OBJEXT) bookmarks_dpi_OBJECTS = $(am_bookmarks_dpi_OBJECTS) bookmarks_dpi_DEPENDENCIES = @@ -81,7 +83,7 @@ depcomp = $(SHELL) $(top_srcdir)/depcomp am__depfiles_maybe = depfiles @AMDEP_TRUE@DEP_FILES = ./$(DEPDIR)/bookmarks.Po \ @AMDEP_TRUE@ ./$(DEPDIR)/downloads.Po ./$(DEPDIR)/ftp.Po \ -@AMDEP_TRUE@ ./$(DEPDIR)/hello.Po ./$(DEPDIR)/https.Po +@AMDEP_TRUE@ ./$(DEPDIR)/hello.Po ./$(DEPDIR)/https.Po COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) CCLD = $(CC) @@ -198,6 +200,7 @@ downloadsdir = $(libdir)/dillo/dpi/downl ftpdir = $(libdir)/dillo/dpi/ftp httpsdir = $(libdir)/dillo/dpi/https hellodir = $(libdir)/dillo/dpi/hello +xprotodir = $(libdir)/dillo/dpi/xproto bookmarks_dpi_LDADD = @GLIB_LIBS@ downloads_dpi_LDADD = @GLIB_LIBS@ ftp_filter_dpi_LDADD = @GLIB_LIBS@ @@ -333,6 +336,28 @@ uninstall-helloPROGRAMS: clean-helloPROGRAMS: -test -z "$(hello_PROGRAMS)" || rm -f $(hello_PROGRAMS) + +install-xprotoPROGRAMS: $(xproto_PROGRAMS) + @$(NORMAL_INSTALL) + test -z "$(xprotodir)" || $(mkdir_p) "$(DESTDIR)$(xprotodir)" + @list='$(xproto_PROGRAMS)'; for p in $$list; do \ + p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \ + if test -f $$p \ + ; then \ + f=`echo "$$p1" | sed 's,^.*/,,;$(transform);s/$$/$(EXEEXT)/'`; \ + echo " $(INSTALL_PROGRAM_ENV) $(xprotoPROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(xprotodir)/$$f'"; \ + $(INSTALL_PROGRAM_ENV) $(xprotoPROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(xprotodir)/$$f" || exit 1; \ + else :; fi; \ + done + +uninstall-xprotoPROGRAMS: + @$(NORMAL_UNINSTALL) + @list='$(xproto_PROGRAMS)'; for p in $$list; do \ + f=`echo "$$p" | sed 's,^.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \ + echo " rm -f '$(DESTDIR)$(xprotodir)/$$f'"; \ + rm -f "$(DESTDIR)$(xprotodir)/$$f"; \ + done + install-httpsPROGRAMS: $(https_PROGRAMS) @$(NORMAL_INSTALL) test -z "$(httpsdir)" || $(mkdir_p) "$(DESTDIR)$(httpsdir)" @@ -480,7 +505,7 @@ check-am: all-am check: check-am all-am: Makefile $(PROGRAMS) installdirs: - for dir in "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)"; do \ + for dir in "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(xprotodir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)"; do \ test -z "$$dir" || $(mkdir_p) "$$dir"; \ done install: install-am @@ -530,7 +555,7 @@ info: info-am info-am: install-data-am: install-bookmarksPROGRAMS install-downloadsPROGRAMS \ - install-ftpPROGRAMS install-helloPROGRAMS \ + install-ftpPROGRAMS install-helloPROGRAMS install-xprotoPROGRAMS \ install-httpsPROGRAMS install-exec-am: @@ -560,7 +585,7 @@ ps-am: uninstall-am: uninstall-bookmarksPROGRAMS uninstall-downloadsPROGRAMS \ uninstall-ftpPROGRAMS uninstall-helloPROGRAMS \ - uninstall-httpsPROGRAMS uninstall-info-am + uninstall-httpsPROGRAMS uninstall-xprotoPROGRAMS uninstall-info-am .PHONY: CTAGS GTAGS all all-am check check-am clean \ clean-bookmarksPROGRAMS clean-downloadsPROGRAMS \ @@ -570,14 +595,14 @@ uninstall-am: uninstall-bookmarksPROGRAM html-am info info-am install install-am \ install-bookmarksPROGRAMS install-data install-data-am \ install-downloadsPROGRAMS install-exec install-exec-am \ - install-ftpPROGRAMS install-helloPROGRAMS \ + install-ftpPROGRAMS install-xprotoPROGRAMS install-helloPROGRAMS \ install-httpsPROGRAMS install-info install-info-am install-man \ install-strip installcheck installcheck-am installdirs \ maintainer-clean maintainer-clean-generic mostlyclean \ mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \ tags uninstall uninstall-am uninstall-bookmarksPROGRAMS \ uninstall-downloadsPROGRAMS uninstall-ftpPROGRAMS \ - uninstall-helloPROGRAMS uninstall-httpsPROGRAMS \ + uninstall-xprotoPROGRAMS uninstall-helloPROGRAMS uninstall-httpsPROGRAMS \ uninstall-info-am # Tell versions [3.59,3.63) of GNU make to not export all variables. diff -pruN dillo-0.8.2/dpi/xproto.filter.dpi dillo-0.8.2-xproto/dpi/xproto.filter.dpi --- dillo-0.8.2/dpi/xproto.filter.dpi 1969-12-31 20:30:00.000000000 -0330 +++ dillo-0.8.2-xproto/dpi/xproto.filter.dpi 2004-10-31 09:44:40.000000000 -0330 @@ -0,0 +1,64 @@ +#!/bin/bash +read -d'>' dpip_tag + +url=${dpip_tag##*url=\'} +url=${url%\'} +dproto=${url%%:*} +ddata=${url#*:} + +confdir="$HOME/.dillo" +if [ ! -d "$confdir" ]; then + if ! mkdir $confdir; then + msg="Error, could not make directory $confdir" + fi +else + conffile="$confdir/xprotorc" +fi + +if [ "$conffile" ]; then + if [ ! -e "$conffile" ]; then + echo " +# %d is replaced with just the data after the : +# %s is replaced with the full url +ed2k; ed2k.sh %s +mailto; sylpheed --compose %d +rtsp; realplay %s +gg; dillo http://www.google.com/search?q=%d" > $conffile + fi + if [ -e "$conffile" ]; then + while read line; do + line=${line%%#*} + fproto=${line%%;*} + if [ x"$fproto" = x"$dproto" ]; then + handler=${line#*;} + break + fi + done < $conffile + else + msg="Error, could not create file $conffile" + fi +fi + +if [ "$handler" ]; then + handler=${handler//\\%s/"$url"} + handler=${handler//\\%d/"$ddata"} + msg="Using: $handler" + output=$($handler &) +else + msg="No handler registered for protocol: $dproto +Please edit the config file: $conffile" +fi + +cat <<EOF +<dpi cmd="start_send_page" url="dpi:/xproto/xproto.filter.dpi"> +Content-type: text/html + +<html> +<head><title>Xproto Feedback</title></head> +<body> +<hr><h1>Xproto Feedback</hq><hr> +<pre>$msg</pre> +<h3>Command Output, If Any:</h3> +<pre>$output</pre> +</body></html> +EOF diff -pruN dillo-0.8.2/src/capi.c dillo-0.8.2-xproto/src/capi.c --- dillo-0.8.2/src/capi.c 2004-05-21 19:43:07.000000000 -0230 +++ dillo-0.8.2-xproto/src/capi.c 2004-10-31 06:03:28.000000000 -0330 @@ -247,6 +247,9 @@ gint a_Capi_url_uses_dpi(gchar *url_str, } else if (g_strncasecmp(url_str, "https:/", 7) == 0) { server = g_strdup("https"); + + } else { + server = g_strdup("xproto"); } return ((*server_ptr = server) ? 1 : 0); diff -pruN dillo-0.8.2/src/IO/Url.c dillo-0.8.2-xproto/src/IO/Url.c --- dillo-0.8.2/src/IO/Url.c 2004-05-21 19:43:29.000000000 -0230 +++ dillo-0.8.2-xproto/src/IO/Url.c 2004-10-31 06:19:57.000000000 -0330 @@ -108,6 +108,6 @@ ChainFunction_t a_Url_get_ccc_funct(cons if ( j == KeyLen ) return cccList[i].cccFunction; } - return NULL; + return a_Dpi_ccc; } -- Lee Bigelow Blatch Enterprises <ligelowbee(a)yahoo.com>

2 1

[Dillo-dev]meta refresh patch for 0.8.2
by Roberto A. Foglietta Oct. 30, 2004

Oct. 30, 2004

Hi to all, actually I'm working for a local public transport company in which I have to develop a new way to display time table and information to people. Using Dillo into embedded linux system allow my collegues to change graphical display just editing php code in the server BUT this kind of information have to stay up-to-date. Commit a refresh from server is, in this case, the best solution I can immagine. So supporting meta refresh tag makes Dillo good for embedded client systems. This is the main reason because I developed this web-deprecated but very-useful-in-embedded function. In addition to this pratical consideration I think people use free software to be free, so it makes sense give them the freedoom to choose also deprecated functions. Obviously to respect Dillo's team decision to do not allow refresh as default policy I make it optional by setting a flag from command line The patch is plenty of /* RAF, 2004-10-XX: bla bla */ comments because they are usefull for others developers inside my company when they will patch an original version of Dillo and found quickly what I have changed in. If you agree to apply this patch to future stable branches this kind of comments are not any more usefull. If you will include my patch, in agreement with gpl, please inserit somewhere a noticed of code-contribution refering me and the company which is employing me actually. Patch doens't add the memory leak bug which I submit, simply it was the way I discovered that bug. Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

4 5

[Dillo-dev]unsubscribe methods
by Patrick Shanahan Oct. 30, 2004

Oct. 30, 2004

* Haines Brown <brownh(a)hartford-hwp.com> [10-29-04 19:40]: > I've tried to get myself unsubscribed to this list (to which someone > kindly subscribed me without my knowledge or permission), by emailing > the admistrator, but it seems my letter ended up on hold > somewhere. Would somone kindly suggest an alternative method for me to > unsubscribe? There's no facility on the web page for doing so. there is a mailto address in every header from dillo-dev and webpage provision in the trailer mailto:dillo-dev-request@lists.auriga.wearlab.de?subject=unsubscribe http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev directions for unsubing appear in the bottom section of the web page. ps: it is also common curtesy to give a subject indicative of the message content and to *not* hijack threads. Please have a good day and remember: read the instructions provided. -- 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

1 0

[Dillo-dev]Re: dillo patch: anchor names
by Jorge Arellano Cid Oct. 29, 2004

Oct. 29, 2004

Matthias, Maybe the most important guideline in this answer is that we're trying to provide good hint-messages for common HTML bugs, not being as picky (or correct) as the W3C's validator. The two main reasons behind this are that first, we do not want to (nor can) complicate too much the code inside dillo (some big browsers have several parsers inside), and we want to help to fix the most problematic HTML bugs (mainly nesting), not all. BTW, inside Dillo all the HTML-like content is currently parsed as HTML-4.01 with a few minor exceptions. HTML-4.01 is a good default because it tries hard to be backwards compatible. The third reason is that if the need for a formal validation arises, the W3C does a great job on it! :) On Wed, Oct 13, 2004 at 06:20:36PM +0200, Matthias Franz wrote: > Dear Jorge, > > here is the anchor name patch I promised you long time ago. > It does the following: > > * First of all, it evaluates the <!doctype> tag to find out whether > the document is HTML or XHTML. If the tag is wrong or missing, an > error is raised. Parsing <!doctype ...> is a good idea. Putting that info in a structure like this one: typedef enum { DT_NONE, DT_HTML, DT_XHTML } DocumentType; typedef struct { DocumentType Type; float Version; } DocumentInfo; allows for having all the information in one place, and to later decide whether to take some action or not. e.g. DT_NONE + DT_HTML + 4.01 means no doctype was given and that HTML-4.01 is assumed as default. DT_HTML + 4.01 means it was stated explicitly in doctype. > > * Dillo now distinguishes more carefully between head and body section There was a bug in dillo (up to rc1). A patch is now in CVS. When the HTML meta refresh warning was sent, it switched from IN_HEAD to IN_BODY. Note that for HTML-4.01: BODY: Start tag: optional, End tag: optional HEAD: Start tag: optional, End tag: optional > * The errors "<...> not allowed in body section" are now centralised > in Html_process_tag Could be. > Moreover, errors are raised in the following situations: > (After all, this was the goal!) > > * if an anchor name (defined by "name" or "id") is already defined OK. > For performance reasons, I have changed (very) few lines in dw_page.c > and dw_gtk_viewport.c. (pending as for the latest bugs found...) > > * if (in HTML mode) the "name" and "id" tags of <a> differ OK. > * if <a> tags are nested OK. > * extra_warning if an anchor name (defined by "name") was illegal for "id" OK. > > > NOT DONE: > > * warning if in XHTML <a> is used with "name" and no "id" > (according to the spec, this has no effect, which is probably not intended) OK. > * the "refresh" warning causes (like before) an error if further > head elements follow the <meta> Fixed in CVS now (Björn Brill). > > * I've discovered that some parts of the TagInfo structure are not used > any more, for example TagLevel and bits 2^0 = 1 and 2^2 = 4 of Flags. TagLevel is used extensively by the W3C+heuristics mode. Look at Html_tags_get_taglevel() calls. Yes, bits 0 and 2 are not yet used, but there they are just in case they're needed. > In particular, I didn't know how to define them for <!doctype> on line 4281. HTML elements can be of type 'block' or 'inline' (well, also 'flow'). And they can be containers of 'inline' or containers of 'blocks'. This is what the flags are. I'll comment that inside the code. For instance, <address> is an 'block' element, and a cointainer of 'inline' elements. address B8(0110) |||`- inline element ||`-- block element |`--- inline container `---- block container This is well defined here: http://www.cs.tut.fi/~jkorpela/html/nesting.html Now, as !doctype isn't there, an inline element that's a block container can appear almost anywhere (i.e. B8(0101)), and help to tackle the issue. > * IN_BUTTON in html.h is also not used any more; I've replaced it by the > new IN_A. Let IN_BUTTON be. As buttons can't be nested, it was meant to catch that one (not implemented yet). > * One change in Html_process_tag is more of a hack; I didn't want to > start rewriting everything without contacting you first. > > > You see that is still work to do in html.c, all the more because know > one could add error messages based on the distinction between HTML and > XHTML. (E.g., "&#X40;" is illegal in XHTML because of the uppercase "X".) > Would this kind of changes be welcome? Hmmm, I think this is too much by now. > I hope this patch can still make it into rc2. If you have comments or > questions, please let me know. As explained before, it better not be in rc2. Just bug-fixes. -- Regards Jorge.-

4 4

[Dillo-dev]news about memory leak
by Riccardo Mottola Oct. 29, 2004

Oct. 29, 2004

Hey, I am on a NetBSD/ppc system. DIllo 0.8.3 and can reproduce the leak. I noted however that: - clicking the reload button in thight succession gets an increment of about 4K every time - the leak is consitent, you can make the amount of leaked memory skyrocket to megabytes. - clicking slowly, waitning 10 seconds each time does NOT make dillo leak I suspect the leak happens if you click reload before dillo has "finished" the page and the "stop button" is disabled. I used a very simple page: <html>this is a test</html> Cheers, Riccardo

2 2

[Dillo-dev]Protocol Handlers
by Lee Bigelow Oct. 28, 2004

Oct. 28, 2004

Hello there, I was playing with the dpi's and made one for ed2k:// links (based on the Hello World example). It was just a quicky, and not generally useful, but I was wondering if anyone was working on a general protocol handler. Along these lines: - Dillo doesn't recognize the protocol so sends it to say external.dpi - external.dpi reads an external.conf file that has a list of protocols and respective external handlers. - If it finds a matching protocol it sends the url(%s), or just the url data (%r), to the handler. - If there's no matching protocol it could show an edit page (like bookmarks modify) for the external.conf. This could be used for mailto:, nntp:, telnet:, etc.. Anyhow, I starting playing with it, and I thought I should check to see if anyone else was also working on it before I went any further. Also, if there's any advice on the approach, or code I should look at, that would be cool. I am no expert C programer, I'm just reading the docs and modifying the code the other fellows already did. (I hope that's ok) -- Lee Bigelow <ligelowbee(a)yahoo.com>

2 1

[Dillo-dev]CYGWIN compatibility
by Jorge Arellano Cid Oct. 28, 2004

Oct. 28, 2004

Hi, Sometime ago I forwarded this message to dillo-dev: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-October/002295.html <q> Hi anyone, I successfully compiled and installed dillo-0.8.2 on an AMD K7 600MHz: $ uname -a CYGWIN_NT-5.0 fermat 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin It runs very well, so you can update your compatibility file ;) Greetings, Marianne </q> Has anyone contacted Marianne to know the recipe? -- Cheers Jorge.-

1 0

[Dillo-dev]Re: Dillo
by Jorge Arellano Cid Oct. 28, 2004

Oct. 28, 2004

On Wed, Oct 27, 2004 at 04:48:37PM -0700, Eugenia Loli-Queru wrote: > >>Please note that the front-end of Gnomefiles has been specifically > >>optimized to work well with Dillo, > > > > I noted, good HTML, and it looks pretty too. > > Thanks, I have made sure that our other sites, osnews.com and nmcx.com also > render well. :) Great! > > > If you can add the missing </form> tag, the application-submit > >process on www.GnomeFiles.org may be finished by using a standard > >dillo-0.8.3. That'd be good news for our users. > > Please retry. I have changed the code to allow Dillo and added the missing > tag. Thanks! > Hmm, I can't seem to make dillo login to gnomefiles's dev corner. I have > edited my .dillo/cookiersrc file to say DEFAULT ALLOW but it still doesn't > login... Oh, it's "DEFAULT ACCEPT". BTW, I use: <q> DEFAULT DENY [...] www.gnomefiles.org ACCEPT_SESSION <q> > Do you have a better luck with it? Yes! By using a standard dillo-0.8.3, I was able to go through the whole process without any hassle. As a result, Dillo has now its own record at www.gnomefiles.org, and it's the first on the "Latest Software" list at the time of this writing. Thanks for your help. -- Cheers Jorge.-

1 0

[Dillo-dev]dillo-0.8.3 officially released!
by Jorge Arellano Cid Oct. 27, 2004

Oct. 27, 2004

Hi there, Finally the release process saw the light, and today the new dillo-0.8.3 was released! It went through a long testing process so we expect this one to be very stable and to have a good reception. The announcement was just submitted to freshmeat and it should appear in some minutes. Thanks to all the people that contributed to test the release candidates with their time and feedback. Go get it! Now, we'll focus on the next big steps. That's the FLTK port, new Dw abstraction layer, review of the CCC, caching, etc. We're preparing a prioritized tasks list with Sebastian and it will make it into its own HTML page. Sebastian: feel free to merge the new Dw abstraction layer into the CVS. Let's start this ASAP. -- Cheers Jorge.-

1 0

[Dillo-dev]dillo-0.8.3-rc3
by Jorge Arellano Cid Oct. 26, 2004

Oct. 26, 2004

Hi there, The tarball for dillo-0.8.3-rc3 is ready for download and testing. This is rc2 plus the fixes for cookies and the redirection loop (i.e. not current CVS). Please test it with sites that use cookies (as advogato) and with pages that use HTTP redirections (not meta-refresh). That's the emphasis area; the other aspects have been throughly tested during this cycle. Get it from: http://www.dillo.org/download/dillo-0.8.3-rc3.tar.bz2 The plan is to announce 0.8.3 on Wed 27. Please send your feedback! -- Cheers Jorge.-

5 14

[Dillo-dev]Possible RPM delays
by Kelson Vibber Oct. 25, 2004

Oct. 25, 2004

My main computer at home has been having problems lately. I *hope* it's just the video card (I would expect worse problems if it were the motherboard, CPU, or memory), but I think it's fair to warn you that if 0.8.3 final comes out before I've resolved the issues, I might not be able to build all the RPMs immediately. Kelson Vibber www.hyperborea.org

4 6

Re: [Dillo-dev]Caching
by Jorge Arellano Cid Oct. 22, 2004

Oct. 22, 2004

Brian, On Fri, Oct 22, 2004 at 09:00:27AM -0400, Brian Hechinger wrote: > > > ok, i will volunteer to do the caching portion. > > > > Good! We need developer power. > > and i need more experience. this'll be good for me. ;) > > > Read the docs, and when in the code, after the normal path, > > follow the End2End reload flag. You can also look how it is > > handled with plugins. > > i will do that today, i'll let you know what i can figure out on my own. > > > Beware: don't dig inside the CCC or you'll ge lost. I'm > > preparing a document on it, and without this material, it'd be > > almost impossible to figure it out. > > ok, then i'll be very careful to avoid it for now. ;) > > > It looks like a good idea to start with. Flexible and simple. > > that's what i was striving for. no need to add extra complexity for no good > reason. ;) > > > Caching is complex. Pragma inside meta whithin HTML is just one > > way. HTTP has several others (for instance you'll have to start > > reading at section 13 of rfc2068.txt (aka HTTP1.1). > > ok, in that case i propse to add Pragma first and once i get that working i'll > add the other methods as well. > > > To make things more interesting, if an RFC-compliant user agent > > (browser) is built, then it's very easy to abuse it. By sending > > no-cache directives for advertising for instance. > > hence the need for cacherc so that we can specify which servers we will honor > the no cache directive from. this is something we need to certain things to > work right, but like you said, we don't want to get abused by it either. > > > I hope this gets you started. When in doubt, please ask. > > i still have to go through End2End, but real quick, how would i go about > parsing the header looking for Pragma? what's the best place to do that? Look inside Cache_parse_header(). :-) -- Cheers Jorge.-

1 0

[Dillo-dev]dillo don't handle the html euro symbol
by Florent BERANGER Oct. 22, 2004

Oct. 22, 2004

Hi everyones, Dillo don't handle the € HTML symbol. ? Best regards, Florent ************************ ADSL ILLIMITE TISCALI + TELEPHONE GRATUIT ************************ Surfez 40 fois plus vite pour 30EUR/mois seulement ! Et téléphonez partout en France gratuitement, vers les postes fixes (hors numéros spéciaux). Tarifs très avantageux vers les mobiles et l'international ! Pour profiter de cette offre exceptionnelle, cliquez ici : http://register.tiscali.fr/adsl (voir conditions sur le site)

2 1

[Dillo-dev]about gtk2.diff.gz
by Calvin Yu Oct. 21, 2004

Oct. 21, 2004

I used this patch file, tried dillo-0.7.3 and dillo-0.8.0. But when they were patched, both of them occured errors. Is there another version between 0.7.3 and 0.8.0 that can be patched with gtk2.diff.gz exactly. Who can send me that version, i just want to have a test. i will be very grateful for your help. My mail box is yuzenghui(a)people.com.cn Or yuzenghui(a)hotmail.com Thank you!!

3 2

[Dillo-dev]html parser stress testing?
by Thorben Thuermer Oct. 21, 2004

Oct. 21, 2004

Hello, (i just noticed this has been reported already, but anyway) a bit ago somebody reported a interesting experiment on bugtraq: he wrote a script that generates random malformed html and used it to test the stability (and security, in case bugs could be exploited to execute code!) of various browsers: http://www.securityfocus.com/archive/1/378632/2004-10-15/2004-10-21/0 this would probably also be interesting to test dillo with (running in a debugger) to weed out bugs. and just a bit after i thought that, somebody reported the first: http://home.eggdrop.ch/cgi-bin/remangle.cgi?0x702d9be9 <TABLE><TD COLSPAN=400192481> -> segfault - Thorben

2 1

[Dillo-dev]Rendering bug...
by Jorge Arellano Cid Oct. 21, 2004

Oct. 21, 2004

Hi Sebastian, Do you remember sometime ago when I lost a page that showed an overlayed calendar. Well, I was browsing dock apps an came accross this one: http://www.dockapps.org/file.php/id/99 This time I saved it! :) It reliably reproduces the bug: overlayed text rendering. Please give it a look. The bug shows on 0.8.2 and 0.7.3 so it's old enough that rc3 can perfectly get out with it inside, just in case it is not a trivial fix. -- Cheers Jorge.-

1 0

RE: [Dillo-dev]which version does this patch file patch
by Linda J. Laubenheimer Oct. 21, 2004

Oct. 21, 2004

> -----Original Message----- > From: dillo-dev-admin(a)lists.auriga.wearlab.de > [mailto:dillo-dev-admin@lists.auriga.wearlab.de] On Behalf Of > Sebastian Geerken > Sent: Monday, October 04, 2004 10:58 AM > To: dillo-dev(a)lists.auriga.wearlab.de > Subject: Re: [Dillo-dev]which version does this patch file patch > > > Hi, > > On Mon, Oct 04, yuzenghui wrote: > > hello everybody, I found a patch file in > > http://www.dillo.org/misc_files/gtk2.diff.gz. which version > of dillo > > can use this patch? And does this patch upgrade dw to gtk2? > > This patch can be (at least) applied to the version from > October 2003, but (most likely) not with the current version > of dillo. This patch is furthermore rather early development. > > The plans to port dillo to Gtk2 have been given up (and there > does not seem to be interest in this at all), so you should > not expect it to be continued. *Headdesk* So that's why it won't compile with glib2 and gtk2. It always ended up linking against libmodule 1.2, libglib 1.2, etc., if it compiled at all, because gtk+ apparently links against those, regardless of what you tell it in gtk-config. Oh, well, no Dillo on my thin box. If you have to install two versions of a library, you've done something wrong. The other stuff on the box wants the later libraries (glib2, gtk2). I'm not a C programmer, otherwise I'd fix it and send it to you. ljl

6 8

[Dillo-dev]Bug #364
by Russell J. Wood Oct. 21, 2004

Oct. 21, 2004

Hello Dilldoers =b Would the said bug be because the Set-Cookie entity sent from advogato.org is not RFC compliant? Here is what I received: Set-Cookie: id=<data>; path=/; Expires=Thursday, 20-Oct-2005 11:57:18 GMT I'm under the impression the Expires attribute is meant to be as: Wdy, DD-MM-YYYY HH:MM:SS GMT Therefore, because the Weekday isn't in an abbreviated form it is being discarded? Regards, Russell

3 7

[Dillo-dev]dillo-0.8.3-rc2 ready for download
by Jorge Arellano Cid Oct. 21, 2004

Oct. 21, 2004

Hi there, The new dillo-0.8.3-rc2 is ready for download and testing! It's basically the same as rc1, but with the race condition on the file dpi solved. It also uses a dpi server instead of a dpi filter so please beware and remove: /usr/local/lib/dillo/dpi/file/file.filter.dpi or /usr/lib/dillo/dpi/file/file.filter.dpi Actually it can work with both, but as we want to test the dpi server in the tarball (default) please be careful and be sure to remove the file filter dpi to be testing the file server dpi. (the other change is a minor improvement on the visited link color choosing algorithm). Feedback is very welcomed. After you say it's OK, it will be officially announced as dillo-0.8.3. Download URL: http://www.dillo.org/download/dillo-0.8.3-rc2.tar.bz2 -- Cheers Jorge.-

4 5

[Dillo-dev]Re: comment from ps2 group on 0.8.x
by Jorge Arellano Cid Oct. 20, 2004

Oct. 20, 2004

On Tue, Oct 19, 2004 at 07:33:18PM +0100, robert w hall wrote: > > > > Jorge > This from playstation2 group - I've asked him to ty the rc2 version > and/or clarify which 0.8.x version didn't render properly > Bob Hall Thanks. I received this email and the former on my personal email address. AFAIU you're on dillo-dev so I answered there, and to be sure this one goes to dillo-dev and to your address. Please use dillo-dev in the future. The main problem with writing directly to me is that I end being the only one that knows what's going on! :-) (Ah, and there's also the problem of duplicate answers...) > > ________________________________________________________________________ > > Read and respond to this message at: > https://playstation2-linux.com/forum/message.php?msg_id=45864 > By: deesaid Oh, please forward this in my name to that group. > > I have a problem with 0.8.x versions in PS2: some pages that look > correct with > the older dillo (the one that's precompiled here), when I try them with > the > newer 0.8.x versions look unformatted. The simplest example is doing a > search > on google: at the search results page, in a regular browser you can see > the > google logo at the top, the search form to the right, and below the logo > and > the form, the search results. In 0.8.x versions the results page is > composed > by the Google logo at the left top and the search form at the right, but > the > results are shown just below the search form, leaving a hughe blank > margin below > the google logo. > > Is there a way to fix it? Yes, the new parser (W3C + heuristics) solves this problem. RC2 will work and so 0.8.3. -- Cheers Jorge.-

2 3

[Dillo-dev]Hello to all and first question
by Roberto A. Foglietta Oct. 20, 2004

Oct. 20, 2004

Hi, first of all: thank you very much for you great job in doing Dillo! Actually I'm trying to use it to display bus time table in a station. What I'm looking here? A /deprecated/ features! I need to reload _automatically_ pages on the bus-station screens, there are some ways to do that: 1) use deprecated meta refresh tag (not work, even in previous vers.) 2) modify Dillo code to accept a -r <n> flag which force him to reload every <n> seconds 3) writing a dpi plugin (???) The way n.1 could be the best for me because I could choose reload delay just from server inserting that deprecated flag in HTML code. But old version of Dillo like 0.2.4 - 0.6.1 don't do that. Simply moved on the specified url and nothing else about reload. I would find a solution should be usefull for everybody and quite simple to do. Like put a flag which enable that deprecated tag and do it working. Or it could be better do something else? Automatically reload should be very usefull in all embedded (but not pda) system which aim to keep some information on the screen refreshed. That for all. Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

1 0

[Dillo-dev]interesting link about browsers security tests
by Florent BERANGER Oct. 20, 2004

Oct. 20, 2004

Hi, http://www.securityfocus.com/archive/1/378632/2004-10-15/2004-10-21/2 Best regards, Florent ************************ ADSL ILLIMITE TISCALI + TELEPHONE GRATUIT ************************ Surfez 40 fois plus vite pour 30EUR/mois seulement ! Et téléphonez partout en France gratuitement, vers les postes fixes (hors numéros spéciaux). Tarifs très avantageux vers les mobiles et l'international ! Pour profiter de cette offre exceptionnelle, cliquez ici : http://register.tiscali.fr/adsl (voir conditions sur le site)

1 0

[Dillo-dev]Dillo Bug #577
by Russell J. Wood Oct. 20, 2004

Oct. 20, 2004

Hello Jason, I'm not sure how long ago you posted that bug, but it isn't a Dillo bug. The reason /usr/bin/dpid was executed is because it would have been before /usr/home/jason/bin in the PATH variable. Try moving your ~/bin directory before /usr/bin and see if you get the same results. Regards, Russell

1 0

[Dillo-dev]Bug #514
by Russell J. Wood Oct. 20, 2004

Oct. 20, 2004

Hello all. Bug number 514 isn't really a bug, per-se, due to the fact that an XHTML style script tag (<script src="java.js" type="text/javascript" />) isn't permitted in the head. Rendering it would be the bug, in my opinion. Regards, Russell

1 0

Re: [Dillo-dev]dillo-0.8.3-rc2 ready for download
by Jorge Arellano Cid Oct. 19, 2004

Oct. 19, 2004

On Tue, Oct 19, 2004 at 10:16:34AM +0100, robert w hall wrote: > In article <20041018191501.GM9792(a)dillo.org>, Jorge Arellano Cid > <jcid(a)dillo.org> writes > >Hi there, > > > > The new dillo-0.8.3-rc2 is ready for download and testing! > > > > It's basically the same as rc1, but with the race condition on > >the file dpi solved. It also uses a dpi server instead of a dpi > >filter so please beware and remove: > > > > /usr/local/lib/dillo/dpi/file/file.filter.dpi or > > done - :-) :-) > > [...] > > Feedback is very welcomed. After you say it's OK, it will be > >officially announced as dillo-0.8.3. > > > > Download URL: > > > > http://www.dillo.org/download/dillo-0.8.3-rc2.tar.bz2 > > > > > seems to compile OK on a playstation2 with https enabled > > dpi_parse_token gives an ERROR from open_url each time when trying to > read the filename, > before successfully executing start_send_page... > I presume this is an intended untidyness ? Yes. Before sending the dpi request to the server, a tentative connection is made to be sure it is running. If it's not, a new server is launched. Notwithstanding the untidiness exists ;), essentially it consists in giving a scary message instead of a more meaningful one. > Keep up the good work Thanks. We hope to. -- Cheers Jorge.-

1 0

[Dillo-dev]Re: Dillo potential DOS via redirect loop
by Jorge Arellano Cid Oct. 19, 2004

Oct. 19, 2004

Hi Kelson, On Mon, Oct 18, 2004 at 04:39:34PM -0700, Kelson Vibber wrote: > I was attempting to pull up the bug database for Wordpress > <http://mosquito.wordpress.org/> in Dillo 0.8.3rc2, and noticed that the > browser froze when I clicked on the "View bugs" link. After I killed it > and re-launched it from a command line, I saw it spewing Nav_open_url > messages over and over, alternating between these two lines: > > Nav_open_url: Url=>http://mosquito.wordpress.org/view_all_bug_page.php< > Nav_open_url: Url=>http://mosquito.wordpress.org/view_all_set.php?type=0< Yes, it happens... > > I'm not entirely sure what the site is trying to do, but Firefox, Opera > and IE all seem to make it through okay. I suspect it's something like > this: > > 1. view_all_bug_page.php checks for a cookie. It doesn't find it, so it > redirects (302) to view_all_set.php?type=0 > 2. view_all_set.php sets the cookie, then sends the browser back to the > original page. > 3. Either Dillo hasn't accepted the cookie and view_all_bug_page.php > sends the redirect again, or Dillo has already cached the 302 response > and jumps to view_all_set.php anyway. > > Adding mosquito.wordpress.org to cookiesrc doesn't make a difference. Currently Dillo's cache is handling HTTP 30x answers as cacheable redirections. This is more a lack of implementation than a BUG (there's no code to handle 302 answers now). > > Based on the libwww-perl HEAD utility (which breaks out of the loop > after 7 redirects) and just telnetting to port 80, I've found the following: > > - They're using a 302 (temporary) redirect on both scripts > - They're setting a cookie on view_all_set.php. > - They're using relative URLs in the Location header (which I think is > technically not allowed, but has been used in practice for years.) Dillo handles relative locations. > Regardless of whether this setup is valid, it *does* make Dillo stop > responding. There is at least one bug here -- Dillo isn't detecting the > redirect loop and breaking out of it -- and possibly two (if it's > caching the 302/temporary status). Yes, there're two problems. Dillo hogging the CPU is a BUG that'd be better fixed for 0.8.3. The caching problem is a large issue that needs much more time to tackle. The cache problem is very interesting: if a browser happens to follow the SPEC, it becomes easy to abuse (e.g. pragma: no-cache advertising). OTOH, some sites can require to refresh some page contents in order to keep some meaningful state (HTTPS services usually use cache directives). Maybe as it happens with cookies, just allowing certain cites and honoring HTTP cache directives from that set only, is a good solution in the long term. I'll try to find a way to catch the redirection loop hog... -- Cheers Jorge.-

1 0

[Dillo-dev]Re: anchor names
by Matthias Franz Oct. 19, 2004

Oct. 19, 2004

Dear Sebastian, thanks for the quick bugfix. On Sun, Oct 17, 2004 at 04:32:09PM +0200, Sebastian Geerken wrote: > The changes also make the viewport check, whether anchor names are > unique. If not, g_return_if_fail is called, which messages should not > be printed normally (and "normally" includes faulty web pages), > instead, normal HTML error messages should be shown. Probably, the > best solution is to add a function a_Dw_gtk_viewport_check_anchor(), > which returns, whether an anchor is already defined. If it returns > TRUE, an appropriate message is shown, and the anchor is not added. Why don't you let a_Dw_gtk_viewport_add_anchor return a result: FALSE = ok, TRUE = anchor already defined and not changed Then a_Dw_page_add_anchor could pass this on to html.c, where my patch would produce the HTML warning. Otherwise one would look up the hash table twice, once in a_Dw_gtk_viewport_check_anchor and once in a_Dw_gtk_viewport_add_anchor. All the best, -- Matthias Franz Section de Mathématiques, Université de Genève, Suisse

2 1

Re: [Dillo-dev]Re: race condition patch]
by Jorge Arellano Cid Oct. 18, 2004

Oct. 18, 2004

-- Cheers Jorge.-

1 0

[Dillo-dev]Re: anchor names
by Jorge Arellano Cid Oct. 18, 2004

Oct. 18, 2004

Hi there, This is half an email forward and half an answer. On Sun, Oct 17, 2004 at 04:32:09PM +0200, Sebastian Geerken wrote: > Hi, > > the dillo-dev mailing list does not seem to work, I always get an 550 > error, so I forward you the mail, which I did not succeed to send to > the list. > > Sebastian Now, 18 Oct, it works for me. I'm answering to dillo-dev because my test mail succeeded. > Date: Sun, 17 Oct 2004 15:54:40 +0200 > From: Sebastian Geerken <sgeerken(a)dillo.org> > Subject: Re: [Dillo-dev]anchors_table not cleared > To: dillo-dev(a)auriga.wearlab.de > Mail-Followup-To: Sebastian Geerken <sgeerken(a)dillo.org>, > dillo-dev(a)auriga.wearlab.de > > On Fri, Oct 15, Matthias Franz wrote: > > I'm writing a patch for a better treatment of anchor names in HTML pages. > > During this, I've come across the following bug in Dillo. > > > > Jorge: I think this is what produced the bug in the patch I sent you. > > > > Entries are never removed from the hash table anchors_table, which stores > > the anchors of a page (see dw_gtk_viewport.c). This means that whenever a > > new page is displayed in the same viewport, the old anchors remain in > > the hash table, but their keys are overwritten. Like in this example: > > (The "###" lines are debug information I've inserted.) > > > > [...] > > > > Obviously, the anchors_table must be cleared whenever a new page is > > displayed. I don't know the dw* part of Dillo very well, and the > > connection between the html structure and the viewport seems to be quite > > indirect. Can anyone suggest a fix? > > The latest commitment in CVS fixes this, the patch is also > attached. Jorge, I'm not sure, whether this should be included into > the release, since the changes are rather big, and currently, it only > fixes a memory leak. I'd prefer to leave it out of rc2. It's been more than four months since our last release. The one following 0.8.3 is going to have the new abstraction layer for Dw, and other changes, so just in case it takes some time to stabilize it, it'd be very good to have a solid 0.8.3 out there. I'll prepare the dillo-0.8.3-rc2 tarball ASAP and write back when it's ready for download... > > The changes also make the viewport check, whether anchor names are > unique. If not, g_return_if_fail is called, which messages should not > be printed normally (and "normally" includes faulty web pages), > instead, normal HTML error messages should be shown. Probably, the > best solution is to add a function a_Dw_gtk_viewport_check_anchor(), > which returns, whether an anchor is already defined. If it returns > TRUE, an appropriate message is shown, and the anchor is not added. Agreed. -- Cheers Jorge.-

1 0

[Dillo-dev]Is dillo-dev back? (test mail)
by Jorge Arellano Cid Oct. 18, 2004

Oct. 18, 2004

Hi, If this is readable, dillo-dev is up! -- Cheers Jorge.-

1 0

[Dillo-dev]anchors_table not cleared
by Matthias Franz Oct. 15, 2004

Oct. 15, 2004

Hi everybody, I'm writing a patch for a better treatment of anchor names in HTML pages. During this, I've come across the following bug in Dillo. Jorge: I think this is what produced the bug in the patch I sent you. Entries are never removed from the hash table anchors_table, which stores the anchors of a page (see dw_gtk_viewport.c). This means that whenever a new page is displayed in the same viewport, the old anchors remain in the hash table, but their keys are overwritten. Like in this example: (The "###" lines are debug information I've inserted.) ~$ dillo http://www.google.de dillo_dns_init: Here we go! Disabling cookies. ### Dw_gtk_viewport_init: anchors_table init Nav_open_url: Url=>about:splash< Nav_open_url: Url=>http://www.google.de< Dns_server [0]: www.google.de is 0x8100ea8 Connecting to 66.102.9.99 ### size(anchors_table) = 0 ### entries: ### Html_add_anchor: adding anchor 1a ### size(anchors_table) = 1 ### entries: <1a> ### Html_add_anchor: adding anchor 2a ### size(anchors_table) = 2 ### entries: <2a> <1a> ### Html_add_anchor: adding anchor 3a ### size(anchors_table) = 3 ### entries: <3a> <2a> <1a> ### Html_add_anchor: adding anchor 4a ### size(anchors_table) = 4 ### entries: <4a> <3a> <2a> <1a> ### Html_add_anchor: adding anchor all ### size(anchors_table) = 5 ### entries: <4a> <all> <3a> <2a> <1a> ### Html_add_anchor: adding anchor lgr ### size(anchors_table) = 6 ### entries: <4a> <all> <3a> <2a> <1a> <lgr> ### Html_add_anchor: adding anchor cty Nav_open_url: Url=>http://www.google.de/imghp?hl=de&tab=wi&ie=UTF-8< Connecting to 66.102.9.99 ### size(anchors_table) = 7 ### entries: <> <> <h3> <> <¸1> <À(> <> ### Html_add_anchor: adding anchor 0a ### size(anchors_table) = 8 ### entries: <0a> <> <> <h3> <> <¸1> <> <> ### Html_add_anchor: adding anchor 2a ### size(anchors_table) = 9 ### entries: <0a> <> <> <h3> <> <2a> <¸1> <> <> ### Html_add_anchor: adding anchor 3a ### size(anchors_table) = 10 ### entries: <0a> <> <> <h3> <3a> <> <2a> <¸1> <> <> ### Html_add_anchor: adding anchor 4a Dillo: normal exit! Obviously, the anchors_table must be cleared whenever a new page is displayed. I don't know the dw* part of Dillo very well, and the connection between the html structure and the viewport seems to be quite indirect. Can anyone suggest a fix? Thanks in advance, -- Matthias Franz Section de Mathématiques, Université de Genève, Suisse

2 2

[Dillo-dev][marianne@mathematicians.de: Compatibility]
by Jorge Arellano Cid Oct. 15, 2004

Oct. 15, 2004

-- Cheers Jorge.-

1 0

[Dillo-dev]testing dillo-0.8.3-rc1
by Bjoern Brill Oct. 15, 2004

Oct. 15, 2004

Hello, I've tried out dillo-0.8.3-rc1 for a few days on a Debian GNU/Linux 3.0 "woody"/i386 system. It compiled and installed cleanly, and I did not encounter any regressions against 0.8.2 yet. The parser changes are a real improvement -- several formerly problematic sites I've tried work now, and the "Detected HTML errors" view produces much more meaningful results. Two small problems I've encountered: - It seems that, if a pair of <a href="..."> </a> tags contains something illegal, like <div>, then the <a> tags are ignored, rather than the illegal stuff inside. That's suboptimal. As an example, look at http://www.kmelektronik.de/ (admittedly a very broken site, standards-wise). The text fragments "Light-Version Versand" and "Light-Version Shop" near the page bottom should really be links. If this is hard to fix, then don't bother. - This one is not new, but I fixed it a while ago for myself and then forgot about it: the "This page uses the NON-STANDARD meta refresh tag..." warning usually occurs inside <head>, but is immediately sent to the parser, which in turn switches its HTML processing state from IN_HEAD to IN_BODY prematurely. After that, head-only tags like <title> and <base> are ignored. A minimal fix is at the end of the mail. Best regards, Björn Brill -- Bj"orn Brill <brill(a)fs.math.uni-frankfurt.de> Frankfurt am Main, Germany --- dillo-0.8.3-rc1/src/html.c.orig Tue Sep 21 17:42:12 2004 +++ dillo-0.8.3-rc1/src/html.c Tue Oct 5 19:21:42 2004 @@ -3101,7 +3101,11 @@ static void Html_tag_open_meta(DilloHtml /* Send a custom HTML message */ html_msg = g_strdup_printf(meta_template, content, delay_str); - Html_write_raw(html, html_msg, strlen(html_msg), 0); + { + DilloHtmlProcessingState SaveFlags = html->InFlags; + Html_write_raw(html, html_msg, strlen(html_msg), 0); + html->InFlags = SaveFlags; + } g_free(html_msg); } }

2 4

[Dillo-dev]Crash on fast reload for dpi pending...
by Jorge Arellano Cid Oct. 14, 2004

Oct. 14, 2004

Hi there, Please note that hitting reload as a mad man over a dpi-handled URL can crash Dillo. This happens because currently there's no code to account for this case (as there is for the HTTP branch). Thinking about it, there's a possibility of merging the CCC branches into a couple of generic and very powerful ones (much like what the dpi is now). If this design is possible, and succeeds, it would mean much simpler handling of IO, the elimination of a lot of complexity, more stability (all the data would use it and thus be more tested). I'll give it some thought. Not for the next release though... :-) -- Cheers Jorge.-

1 0

[Dillo-dev]dillo-0.8.3-rc1.tar.bz2
by Jorge Arellano Cid Oct. 14, 2004

Oct. 14, 2004

Hi there, The release of dillo-0.8.3 is very close now. Today I prepared the release candidate tarball for it. Please test and send some feedback; the last request for feedback on the CVS had a single answer. !? Get rc1 from: http://www.dillo.org/download/dillo-0.8.3-rc1.tar.bz2 It should be out in early September. -- Cheers Jorge.-

4 10

[Dillo-dev]Webmails compatibility with Dillo 0.8.3rc1
by Florent BERANGER Oct. 12, 2004

Oct. 12, 2004

Hi, Here a little test result about webmails compatibility : Read Compose Horde : ok nok Squirrel : ok ok -> you just have to select a frame and it's ok:) Tiscali : nok nok Ms hotmail: nok nok Google gmail: nok nok Yahoo mail: nok nok Best regards, Florent ************************ ADSL ILLIMITE TISCALI + TELEPHONE GRATUIT ************************ Surfez 40 fois plus vite pour 30EUR/mois seulement ! Et téléphonez partout en France gratuitement, vers les postes fixes (hors numéros spéciaux). Tarifs très avantageux vers les mobiles et l'international ! Pour profiter de cette offre exceptionnelle, cliquez ici : http://register.tiscali.fr/adsl (voir conditions sur le site)

1 0

[jcid@dillo.org: Re: [Dillo-dev]Caching]
by Jorge Arellano Cid Oct. 12, 2004

Oct. 12, 2004

Hi, Here's an email that I mistakenly replied personally instead of to dillo-dev. -- Cheers Jorge.-

1 0