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

Re: [Dillo-dev]Bug #364

by Russell J. Wood

Hello all, Nice research. If you like I'll look into it more before a commitment is made, but from what you've described all four might be the go. I'll search some more tonight. Regards, Russell On Wed, Oct 20, 2004 at 06:58:20PM -0300, Jorge Arellano Cid wrote: > On Wed, Oct 20, 2004 at 08:18:20PM +0800, Russell J. Wood wrote: > > 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? > > Could be... > > This is my second answer because I made some mistakes... > > AFAIK, the most current RFC for cookies is RFC-2965, but it > doesn't say a word about the Expires format. > > The previous spec, RFC-2109 says: > > <q> > Netscape's original proposal defined an Expires header that took a > date value in a fixed-length variant format in place of Max-Age: > > Wdy, DD-Mon-YY HH:MM:SS GMT > </q> > > Note that YY is using two chars here, and that not a word is > said about 'Wdy'. > > http://www.danbbs.dk/~erikoest/hello.htm makes a real soup of > it all: > > In 1996 it was: > <q> > Wdy, DD-Mon-YY HH:MM:SS GMT > expires=Wednesday, 09-Nov-99 23:12:40 GMT > </q> > > *Note the example uses a full weekday name. > > In 1997 it became: > > <q> > The date string is formatted as: > > Wdy, DD-Mon-YYYY HH:MM:SS GMT > > This is based on RFC 822, RFC 850, RFC 1036, and RFC 1123, with > the variations that the only legal time zone is GMT and the > separators between the elements of the date must be dashes. > </q> > > Note the four characters year syntax, and the dashes > requirement. > > As for 'Wdy', RFC-1123 refers to RFC-822 which says day is: > > <q> > day = "Mon" / "Tue" / "Wed" / "Thu" > / "Fri" / "Sat" / "Sun" > </q> > > > RFC-1036 (USENET) which obsoletes RFC-850 says dates must be > acceptable to RFC-822. For instance: > > Dates: Wdy, DD Mon YY HH:MM:SS TIMEZONE > > (that's why the dashes and GMT requirements was added). > > > So that's it. It seems there are four legacy but legal formats: > > Wdy, DD-Mon-YY HH:MM:SS GMT > Wdy, DD-Mon-YYYY HH:MM:SS GMT > Weekday, DD-Mon-YY HH:MM:SS GMT > Weekday, DD-Mon-YYYY HH:MM:SS GMT > > with the second one being the most "correct". > > BTW, the site that Kelson pointed to as an example that uses > cookies and locks dillo on a CPU hog, uses: > > Wdy, DD-Mon-YY HH:MM:SS GMT > > so it's currently ignored. > > I'm working on it now, and found this interesting fact while > testing http://mosquito.wordpress.org/view_all_bug_page.php. > > > AFAIS, we'll have to accept the four date formats... > > Does anyone know better? > Does anyone Wanna' try to find out? > Comments out of simpathetic feelings to a maintainer having a > hard time through the RFCs? :) > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

Oct. 21, 2004

Re: [Dillo-dev]Bug #364

by Jorgen Viksell

Hi, I've been thinking a little bit about it, and have some input on the matter. ons 2004-10-20 klockan 18:58 -0300 skrev Jorge Arellano Cid: > On Wed, Oct 20, 2004 at 08:18:20PM +0800, Russell J. Wood wrote: > > 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? > > Could be... > > This is my second answer because I made some mistakes... > > AFAIK, the most current RFC for cookies is RFC-2965, but it > doesn't say a word about the Expires format. > > The previous spec, RFC-2109 says: It should be noted here that this is said in the "historical" section. And that "Expires" never has been part of an RFC (IIRC). > <q> > Netscape's original proposal defined an Expires header that took a > date value in a fixed-length variant format in place of Max-Age: > > Wdy, DD-Mon-YY HH:MM:SS GMT > </q> > > Note that YY is using two chars here, and that not a word is > said about 'Wdy'. [snip] > So that's it. It seems there are four legacy but legal formats: > > Wdy, DD-Mon-YY HH:MM:SS GMT > Wdy, DD-Mon-YYYY HH:MM:SS GMT > Weekday, DD-Mon-YY HH:MM:SS GMT > Weekday, DD-Mon-YYYY HH:MM:SS GMT > > with the second one being the most "correct". I want to point out here that we don't use the weekday part in any way, so it can be discarded. And the year part is parsed with strtol() in a way that it doesn't matter if it's two or four chars long (there is a check right after it to account for both cases). > > BTW, the site that Kelson pointed to as an example that uses > cookies and locks dillo on a CPU hog, uses: > > Wdy, DD-Mon-YY HH:MM:SS GMT > > so it's currently ignored. > > I'm working on it now, and found this interesting fact while > testing http://mosquito.wordpress.org/view_all_bug_page.php. > > > AFAIS, we'll have to accept the four date formats... I agree. In a perfect world the "Max-Age" attribute would be used everywhere. However, "Expires" has become a de-facto standard (and a badly defined such) which needs alot of "special attention" but it's also a must to have working cookies. > Does anyone know better? Not really... :-) > Does anyone Wanna' try to find out? > Comments out of simpathetic feelings to a maintainer having a > hard time through the RFCs? :) My advice: don't stare directly at it! ;-) Regards, Jörgen

Oct. 20, 2004

Re: [Dillo-dev]Bug #364

by Jorge Arellano Cid

On Wed, Oct 20, 2004 at 08:18:20PM +0800, Russell J. Wood wrote: > 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? Could be... This is my second answer because I made some mistakes... AFAIK, the most current RFC for cookies is RFC-2965, but it doesn't say a word about the Expires format. The previous spec, RFC-2109 says: <q> Netscape's original proposal defined an Expires header that took a date value in a fixed-length variant format in place of Max-Age: Wdy, DD-Mon-YY HH:MM:SS GMT </q> Note that YY is using two chars here, and that not a word is said about 'Wdy'. http://www.danbbs.dk/~erikoest/hello.htm makes a real soup of it all: In 1996 it was: <q> Wdy, DD-Mon-YY HH:MM:SS GMT expires=Wednesday, 09-Nov-99 23:12:40 GMT </q> *Note the example uses a full weekday name. In 1997 it became: <q> The date string is formatted as: Wdy, DD-Mon-YYYY HH:MM:SS GMT This is based on RFC 822, RFC 850, RFC 1036, and RFC 1123, with the variations that the only legal time zone is GMT and the separators between the elements of the date must be dashes. </q> Note the four characters year syntax, and the dashes requirement. As for 'Wdy', RFC-1123 refers to RFC-822 which says day is: <q> day = "Mon" / "Tue" / "Wed" / "Thu" / "Fri" / "Sat" / "Sun" </q> RFC-1036 (USENET) which obsoletes RFC-850 says dates must be acceptable to RFC-822. For instance: Dates: Wdy, DD Mon YY HH:MM:SS TIMEZONE (that's why the dashes and GMT requirements was added). So that's it. It seems there are four legacy but legal formats: Wdy, DD-Mon-YY HH:MM:SS GMT Wdy, DD-Mon-YYYY HH:MM:SS GMT Weekday, DD-Mon-YY HH:MM:SS GMT Weekday, DD-Mon-YYYY HH:MM:SS GMT with the second one being the most "correct". BTW, the site that Kelson pointed to as an example that uses cookies and locks dillo on a CPU hog, uses: Wdy, DD-Mon-YY HH:MM:SS GMT so it's currently ignored. I'm working on it now, and found this interesting fact while testing http://mosquito.wordpress.org/view_all_bug_page.php. AFAIS, we'll have to accept the four date formats... Does anyone know better? Does anyone Wanna' try to find out? Comments out of simpathetic feelings to a maintainer having a hard time through the RFCs? :) -- Cheers Jorge.-

Oct. 20, 2004

[Dillo-dev]html parser stress testing?

by Thorben Thuermer

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

Oct. 20, 2004

Re: [Dillo-dev]dillo-0.8.3-rc2 ready for download

by Jeremy Henty

On Wed, Oct 20, 2004 at 12:05:50AM -0300, Jorge Arellano Cid wrote: > On Wed, Oct 20, 2004 at 12:09:38AM +0100, Jeremy Henty wrote: > > On Mon, Oct 18, 2004 at 04:15:01PM -0300, Jorge Arellano Cid > > wrote: > > > > > ... please beware and remove: > > > > > > /usr/local/lib/dillo/dpi/file/file.filter.dpi or > > > /usr/lib/dillo/dpi/file/file.filter.dpi > > > > Arrgh! This breaks for me. If I don't remove this file > > everything works wonderfully. If I rename it then accessing a > > file:... URL gives me "ERROR: can't start dipd daemon!". > [...] > ps aux | grep dpid > Kill every old dpid that may be running. > 'dpidc stop' or 'kill <pids>' Well, I couldn't find any running dpid processes, but I managed to run 'dpidc stop' (it threw an error until I ran it when dillo was also running, is that expected?), and now it all works. Thanks for your time and help! Cheers, Jeremy

Oct. 20, 2004

Re: [Dillo-dev]Re: comment from ps2 group on 0.8.x

by robert w hall

In article <20041019201134.GC2745(a)dillo.org>, Jorge Arellano Cid <jcid(a)dillo.org> writes >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. Read and respond to this message at: https://playstation2-linux.com/forum/message.php?msg_id=45881 By: deesaid Thanks, it's working perfect with 0.8.3 rc2!!! Nice work :-) _ -- robert w hall

Oct. 20, 2004

Re: [Dillo-dev]Possible RPM delays

by Kelson Vibber

Jorge Arellano Cid wrote: > On Mon, Oct 18, 2004 at 10:39:24PM -0700, Kelson Vibber wrote: >>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. > > Thanks for the notice Kelson. > > Can it be ready for an Oct 25 or 27 release? It should be. It seems to freeze only within a few minutes of turning it on (and then only the local display -- I can still SSH in from another computer, but it won't react to the keyboard & mouse or update the display). I used it for several hours last night, and I've left it running constantly since Monday evening with no apparent problems. (Although trying to boot it on Monday was an interesting experience, one which confirms that it's a hardware issue and not a driver.) At this point I plan to just not turn it off for a few days and look for a new video card on the weekend. In the worst case, I can definitely build for the most current releases of Fedora, Mandrake and SuSE (well, the next-most-current Mandrake, since I haven't installed 10.1 yet). Mdk 10.0 and SuSE 9.1 are on the computer I threw together from spare parts, and I have access to a couple of Fedora Core 2 machines at work. -- Kelson Vibber www.hyperborea.org

Oct. 20, 2004

Re: [Dillo-dev]Possible RPM delays

by robert w hall

In article <417697A2.90307(a)pobox.com>, Kelson Vibber <kelson(a)pobox.com> writes >Jorge Arellano Cid wrote: >> On Mon, Oct 18, 2004 at 10:39:24PM -0700, Kelson Vibber wrote: >>>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. >> >> Thanks for the notice Kelson. >> >> Can it be ready for an Oct 25 or 27 release? I sort of half-promised I'd build a version, with and without https enabled, for the playstation2-linux section this time (the last one they had on rpm was 0.7.x I recollect)... But unfortunately I'm a slackware man m'self, so I'd welcome guidance in this honourable outing! the playstation-2 distro is Kondura/Redhat5 vintage :-( -- robert w hall

Oct. 20, 2004

[Dillo-dev]Hello to all and first question

by Roberto A. Foglietta

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

Oct. 20, 2004

[Dillo-dev]interesting link about browsers security tests

by Florent BERANGER

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)

Oct. 20, 2004