January 2006 - Dillo-dev - lists.mailman3.com

[jcid@dillo.org: Re: [Dillo-dev] Dillo 0.8.5 with gmail]
by Jorge Arellano Cid Jan. 13, 2006

Jan. 13, 2006

-- Cheers Jorge.-

1 0

Dillo 0.8.5 with gmail
by Richard Jan. 13, 2006

Jan. 13, 2006

Hello, I have compiled and installed Dillo 0.8.5 and enabled the https DPI. I am trying to use Dillo to log in to gmail. I have made sure that cookies are enabled for .gmail.com. I am able to get the gmail login page which is served through https but I cannot log in to my account. After clicking on the "Sign In" button and accepting all the certificate warnings messages, I am not redirected to my mailbox and I am stuck on the gmail login page. Does dillo support javascript ? and is that the reason why I cannot login to gmail ? If javascript is the stopper that prevents dillo from being used on gmail, hotmail or yahoo etc... then I am willing to devote some time to get something like SpiderMonkey or some other JS engine to work with Dillo. I was running dillo from the command line and below is the output I got from the console. Notice that dillo seems to die in the https.filter.dpi. I have looked at the mailing archives and I think I saw other people being able to at least login to gmail. So I am not sure what is going on in my case. Is there a later unstable version of Dillo I should use in order to login to gmail ? ============================================================== Dpi_parse_token: [<dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'>] a_Dpiapi_dialog: dpip_tag: <dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'> Dpi_parse_token: [<dpi cmd='start_send_page' url=' https://mail.google.com/mail/images/corner_tl.gif'>] { exiting https.dpi} Dpi: [Dpi_process_io] IOClose Nav_open_url: Url=>https://www.google.com/accounts/ServiceLoginAuth< main.c:154: get_command: dpid tag is NULL : main.c:328: main: get_command failed : {In https.filter.dpi} Dpi_parse_token: [<dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'>] a_Dpiapi_dialog: dpip_tag: <dpi cmd='dialog' msg='The remote certificate cannot be verified20' alt1='Continue' alt2='Cancel'> { exiting https.dpi} Dpi_parse_token: [<dpi cmd='start_send_page' url=' https://mail.google.com/mail/images/corner_tr.gif'>] Dpi: [Dpi_process_io] IOClose ============================================================== Thanks Best regards Richard Ta-Min

1 0

Re: [Dillo-dev] Re: patch: python filter DPI supporting the "data:" scheme from RFC 2397
by Jorge Arellano Cid Jan. 5, 2006

Jan. 5, 2006

Hi Ben, On Fri, Dec 30, 2005 at 03:18:12PM -0800, Ben Wiley Sittler wrote: > yes!let me know when the c translation is uploaded and i will gladly > take a look. i have investigated the mp3 thing further, and basically > dillo is not well-prepared to deal with very long uris, especially not > ones handled by a dpi. probably a maximum should be chosen (max. pipe > buffer size less the size of the overhead bytes for the rest of the > dpi request, maybe?) and anything longer should generate an error > message inside dillo. The patch took some time because it uncovered a subtle parsing bug in Dpip. It's fixed now in CVS. Both the new datauri.c and the dpip fix were commited. This is a no-frills datauri dpi version. There're things to polish. For instance: URI="data:;,test" // empty base64 and media type, ";" should be ignored > > separately, much of the dillo core is unprepared to handle data: URIs; > for instance, it tried to generate filenames when saving that are > longer than the OS and filesystem maximum length, and also slow down > the GUI to unusable speeds due to font metric calculations. > furthermore it did not use the mime-types database to select a > filename extension, so they ended up with very cryptic names. Yes, this can also be improved. > as for the python dpi, maybe keep it as an example in the source tree > but don't install it when doing 'make install', and use the new C > implementation as the default? maybe some python programmer will take > it and turn it into something more useful... It didn't work for me so currently it's not in CVS. > also, do the dpi-handling functions in the python dpi seem correct, or > did i misunderstand the protocol? i was not so sure about the > quoting/escaping mechanisms... This was a bit fuzzy... I changed it a bit and commented much more in dpip/dpip.c. Data URIs are a bit delicate with regard to security. This also needs some work. Although datauri is enabled now, it may be disabled for the next release unless security is stronger. -- Cheers Jorge.-

1 0

Size of the new downloads.dpi
by Michal Nowak Jan. 3, 2006

Jan. 3, 2006

Hi dillo developers, I just compiled the CVS version of dillo (0.86-pre) with the FLTK based downloads.dpi. I see it's statically linked against FLTK, but it's now 450 KiB (here). I think it's quite big. When the whole dillo will be FLTK based, will it be staticaly linked too? Or dynamically, like now with the GTK+ 1.2? Thank you all for great work you do. Michal Nowak

2 1

FLTK2-based GUI dpi for downloads
by Jorge Arellano Cid Jan. 3, 2006

Jan. 3, 2006

Hi there, Let's start 2006 with a nice addition to Dillo. Here's a HOWTO fo the FLTK2-based GUI-dpi for downloads: * Get the latest CVS (it has dpi/downloads.cc) * Get http://www.dillo.org/test/dl_GUI.diff cd dillo; patch -p1 < dl_GUI.diff * Go to http://www.fltk.org/software.php and get the "fltk-2.0.x-r4721.tar.bz2" tarball (or SVN at your option). __you need FLTK 2.0.x, FLTK 1.1.x won't work___ * Install FLTK2 * Build Dillo, install & enjoy! Note to packagers: Don't worry about FLTK2. The resulting dpi binary is statically linked so there're no new dependencies for a package that ships the new GUI-dpi for downloads, and as you'll soon understand, this new dpi is the recommended choice! :-) The idea is to ship this GUI-dpi when Dillo-0.8.6 is released. All: Please test it and let me know to the list you succeeded in the installation process (just to be sure I didn't forget a step in the above instructions). Feedback is welcomed. Tips: The GUI is compact, but has plenty of information. Look at the tooltips (place the mouse cursor over the widgets wait and see; e.g. the filename widget shows the wget log). BTW, I also prepared some XPM Icons for window managers. These are in the Icons page. My Icewm looks very nice with the new 16x16 and 32x32 pair! Enjoy, and have a great 2006! -- Cheers Jorge.-

4 10