October 2004 - Dillo-dev - lists.mailman3.com

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

20 Oct '04

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 20 Oct '04

20 Oct '04

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 20 Oct '04

20 Oct '04

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 20 Oct '04

20 Oct '04

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 20 Oct '04

20 Oct '04

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 19 Oct '04

19 Oct '04

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 19 Oct '04

19 Oct '04

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 19 Oct '04

19 Oct '04

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 18 Oct '04

18 Oct '04

-- Cheers Jorge.-

1 0

[Dillo-dev]Re: anchor names
by Jorge Arellano Cid 18 Oct '04

18 Oct '04

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