December 2003 - Dillo-dev - lists.mailman3.com

Best wishes for year 2004

by Jorge Arellano Cid

Hi There, It's early in the morning here in Chile, and I know that in Europe the clock is around 4 to 6 hours ahead, hopefully still in time to send my greetings and best wishes to all the people scattered around the world that participate of dillo-dev. Somewhere inside this december the Dillo project completed four years of existence and continued development. Please excuse me for not displaying a birthday cake picture at the home page; I didn't have the time, but the will to share and celebrate the event still remains! I spent the last months of this year making the arrangements to be able to keep working on dillo the 2004, and hopefully more... It seems that these efforts will flourish and let me work through this new year with renewed energies and hope: let 2004 be a great year for the Dillo project! Cheers & Best wishes to all! Jorge.-

Dec. 31, 2003

Re: [Dillo-dev] VRML support in Dillo

by Thorben Thuermer

On Sun, 28 Dec 2003 13:37:19 EST Rich3800(a)aol.com wrote: > Does Dillo support display of VRML images? Dillo does currently not support renderer-type plugins that would be needed for inline display of VRML/SVG/flash/java/... content (unless hardcoded into the renderer). this is planned for a to-be-developed dpi2 plugin system as mentioned in: http://www.dillo.org/dpi1.html -

Dec. 30, 2003

VRML support in Dillo

by Rich3800＠aol.com

Does Dillo support display of VRML images?

Dec. 28, 2003

WINNING NOTIFICATION/FINAL NOTICE

by MR. TOM VANAD

RABOAS INTERNATIONAL LOTTERY NTERNATIONAL PROMOTION/PRIZE AWARD DEPT. HOLLAND REFF: OGS/7316786098/03 BATCH: 14/055/IPD /NL WINNING NOTIFICATION/FINAL NOTICE We are pleased to inform you of the result of the RABOAS Lottery International programs held on the 27st of Decbmer 2003. Your e-mail address attached to ticket number 4411465886-629 with serial number 3772-99 drew lucky numbers 7-14-17-23-31-44 which consequently won in the 2nd category, you have therefore been approved for a lump sum pay out of US$100,000.(One Hundred Thousand Dollars)CONGRATULATIONS!!! Due to mix up of some numbers and names, we ask that you keep your winning information confidential untill your claims has been processed and your money remitted into your accaunt. This is part of our security protocol to avoid double claiming and unwarranted abuse of this program by some participants All participants were selected through a computer ballot system drawn from over 100,000 company and 50,000,000 individual email addresses and names from all over the world. This promotional program take place every three years. We hope with part of your winning you will take part in our end of year 50 million Dollars international lottery. To file for your claim,please contact our fiduciary agent MR.DALE MELLOR, E.U.INTERNATIONAL B.V E.mail:dalemell@netscape.net TEL:31 641 684 576 Remember, all winning must be claimed not later than 11 th of January 2004. After this date all unclaimed funds will be included in the next take Please note in order to avoid unnecessary delays and complications please remember to quote your reference number and batch numbers in all correspondence. Furthermore,should there be any change of address do inform our agent as soon as possible.Congratulations once more! from our members of staff and thank you for being part of our promotional program. Note: Anybody under the age of 18 is automatically disqualified. Sincerely yours, MR. TOM VANAD (Winning Co-ordinator)

Dec. 27, 2003

Re: spam-safe and basic auth

by Jorge Arellano Cid

Hi Francis, > [...] > > I was just looking for the spam-safe image blocking patch and > > couldn't find it. Would you mind resending it to me? > > No problem at all. It's included below, updated for current CVS (the > earlier version applied cleanly with a 126-line offset). > > The same caveats as before apply -- there is no "right" answer, so the > choice between omitting the image entirely, faking a submit button, > including a default image, or something else, is pretty arbitrary. > > Faking a submit button is what I went for here, taking inspiration > from http://www.htmlhelp.com/reference/html40/forms/input.html#image > and http://ppewww.ph.gla.ac.uk/~flavell/alt/type-image.html > > If you prefer a different option, I'm sure you're well capable of > coding it ;-) I took the text-submit-button approach (it will also serve for when browsing in "text mode" with Dillo). It took me some time to review it (looks simple but it's not!), I also had to fix a bug... Cheers Jorge.- PS: further testing is welcome! ;)

Dec. 26, 2003

Re: [Dillo-dev] Cache expire header...

by Tom Lisjac

> > With this header, Dillo's stdout messages reported "bad clocks"... so I > > tried sending the same date for Expires and Last-Modified. Dillo's > > stdout came back with: "Forcing min expire 60 on >the url< instead 0". > > What does that mean? > > > you're using my patch? I'm using the cvs version of dillo (0.8.0-pre) that I compiled a few days ago. I wanted to test with a generic Dillo so I didn't apply any patches. > Bad clocks means that the expiration time seems to be in history > (compared to Last-Modified, when this header is present) for dillo at the > time when the header was received, and is so more than 1000 seconds. > These expirations are ignored, because many sites send these for all > their content and it would otherwise cause dillo to always reload > everything on these sites. For you're example - 1998 is very long history. That makes sense... thanks for the explanation. > Forcing min expire 60 - this is configurable using min_page_expire option > in dillorc. When this config option is non-zero, dillo will set expiration > times below this value (in seconds) to the config option value. It was > introduced to give better speed with stupid news sites. I appreciate the performance goal but I'm also concerned that the displayed page reflects the content that the site wants to deliver. For example after a user post, collaborative pages need to display fresh content immediately. > > I really need the content of certain pages to expire immediately when > > viewed. Any suggestions for the correct header parameters would be > > greatly appreciated. > > 1. following dillorc options make it most agressivily reload everything: > query_expire_time="0" > min_page_expire="0" > min_image_expire="0" Noted for client side use. > 2. Use Cache-Control header: > > Cache-Control: no-cache This fixed standard post operations... thank you! I had been sending: header("Cache-Control: no-cache, must-revalidate"); ... but I guess the second parameter was causing a problem. The cache is still a problem on post operations followed by a 302 redirect. After posting a user note to an existing page, my application redirects back to the updated main page+notes. With Dillo the page is displayed from cache and doesn't show the note the user just added. Hitting refresh shows the updated page... but having to do this isn't desireable behavior for a collaborative site. I don't have the version of the app posted that looks nice with Dillo yet but adding a note to the following test page shows the problem. http://theseus.sourceforge.net/ewsbeta/index.php?wiki=DilloTest Thanks for the reply! -Tom

Dec. 24, 2003

Re: [Dillo-dev] Cache expire header...

by Madis Janson

On Sun, 14 Dec 2003, Tom Lisjac wrote: > I've written a small, Dillo friendly wiki/cms system in php that I'm > hoping to release in a few weeks. During testing (today's cvs), I found > that Dillo's cache wasn't expiring the dynamic pages. Here's the header > I was initially using to disable client caching: > > header("Expires: Sun, 22 Mar 1998 20:00:00 GMT"); > header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); > header("Pragma: no-cache"); > header("Cache-Control: post-check=0, pre-check=0"); > > With this header, Dillo's stdout messages reported "bad clocks"... so I > tried sending the same date for Expires and Last-Modified. Dillo's > stdout came back with: "Forcing min expire 60 on >the url< instead 0". > What does that mean? > you're using my patch? (it remainds, that i should try to clean up the cache patch for Jorge... oh well it's not easy work, i'm afraid...) Bad clocks means that the expiration time seems to be in history (compared to Last-Modified, when this header is present) for dillo at the time when the header was received, and is so more than 1000 seconds. These expirations are ignored, because many sites send these for all their content and it would otherwise cause dillo to always reload everything on these sites. For you're example - 1998 is very long history. Forcing min expire 60 - this is configurable using min_page_expire option in dillorc. When this config option is non-zero, dillo will set expiration times below this value (in seconds) to the config option value. It was introduced to give better speed with stupid news sites. > I really need the content of certain pages to expire immediately when > viewed. Any suggestions for the correct header parameters would be > greatly appreciated. 1. following dillorc options make it most agressivily reload everything: query_expire_time="0" min_page_expire="0" min_image_expire="0" 2. Use Cache-Control header: Cache-Control: no-cache

Dec. 21, 2003

Is something wrong with the cvs repository?

by Matthias Pfeifer

I think the cvs version is currently not working. i do cd src cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo login cvs -z3 -d:pserver:anonymous@auriga.wearlab.de:/sfhome/cvs/dillo co dillo cd dillo automake -a autoconf (without outputs) and then ./configure gives ./configure: line 650: syntax error near unexpected toke `AM_INIT_AUTOMAKE(dillo,' ./configure: line 650: `AM_INIT_AUTOMAKE(dillo,0.8.0-pre)' - Matthias Pfeifer, Aachen/Germany

Dec. 19, 2003

ChessBrain: World Record!

by The ChessBrain Network

The ChessBrain Network T o be removed from our mailing list, send an email to support(a)chessbrain.net

Dec. 19, 2003

Re: [Dillo-dev] sending referer

by Andreas Tolfsen

Daniel wrote: >Hi Jan, > >On Fri, Dec 19, 2003 at 01:18:40PM +0100, Jan Stary wrote: > > >>why does Dillo not send the referer header? Without it, I >>cannot use the http://validator.w3.org/check/referer link, >>as appearing on the bottom of my pages. >> >> >referer == evil > >>his is the only problem which keeps mozilla on my machine. >> >> >It's not a problem it's a feature. And the reason I use Dillo not >Mozilla *g* > >Daniel > > Well, personally, I think there should be an option for turning it on and off maybe? Wouldn't that please everybody?

Dec. 19, 2003