- Dillo-dev - lists.mailman3.com

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