[Dillo-dev]Using dillo on SourceForge
Is the SSL-enabled version of dillo-0.8.4 up to managing SourceForge accounts? I'm on the login page at <URL:https://sourceforge.net/account/login.php> but when I click the "Login with SSL" button the page just blinks at me as if I'd refreshed the it. I don't get logged in. Is anyone using a SourceForge account through dillo? Jeremy
On Mon, 4 Apr 2005 20:34:55 +0100 Jeremy Henty <jeremy@chaos.org.uk> wrote:
Is the SSL-enabled version of dillo-0.8.4 up to managing SourceForge accounts? I'm on the login page at <URL:https://sourceforge.net/account/login.php> but when I click the "Login with SSL" button the page just blinks at me as if I'd refreshed the it. I don't get logged in. Is anyone using a SourceForge account through dillo?
You need some of these ssl-patches (with an older dillo) which do not use the dpi interface because SF needs cookies to login. With that, you can use at least the SF installation at auriga.wearlab.de As far as I understand, the https dpi plugin does not handle cookies because the cookies do not find their way to cookies.c So you probably have to wait for the cookies dpi. Greetings Andreas Kemnade
On Sat, Apr 09, 2005 at 07:20:46PM +0200, Andreas Kemnade wrote:
On Mon, 4 Apr 2005 20:34:55 +0100 Jeremy Henty <jeremy@chaos.org.uk> wrote:
Is the SSL-enabled version of dillo-0.8.4 up to managing SourceForge accounts? ...
You need some of these ssl-patches (with an older dillo) which do not use the dpi interface
Are you saying I need to check out a previous version of dillo and forward-port some patches? If so, which version and which patches?
As far as I understand, the https dpi plugin does not handle cookies because the cookies do not find their way to cookies.c So you probably have to wait for the cookies dpi.
Hmm, what's the status of the cookies dpi? Thanks for your help. Cheers, Jeremy
As far as I understand, the https dpi plugin does not handle cookies because the cookies do not find their way to cookies.c So you probably have to wait for the cookies dpi. can you give a url to test it? thanks
Hmm, what's the status of the cookies dpi?
It is almost done, but i need an answer to a big doubt before it. how can a function wait(with a timeout if posible) until the cookies dpi send the answer to dillo after dillo have send to dpi cookies a get_cookies command? more explained: the a_Cookies_get function in dillo send a get_cookies command to cookies dpi, then wait a command from the cookies dpi with the answer and the function return the cookies. I have try to do the same that bookmarks dpi but the function used in it is void. I have try to understand ccc but i get it only superficialy. DarkSpirit/Diego
Hi Diego, On Sat, Apr 23, 2005 at 02:34:07PM +0200, Diego Sáenz wrote:
Hmm, what's the status of the cookies dpi?
It is almost done, but i need an answer to a big doubt before it.
how can a function wait(with a timeout if posible) until the cookies dpi send the answer to dillo after dillo have send to dpi cookies a get_cookies command?
Just let it block. Of course a non-blocking timeout or callback approach can be used (as with DNS or HTTP), but in this case the wait time is so short that it is not worth (it will be faster than bookmarks).
more explained: the a_Cookies_get function in dillo send a get_cookies command to cookies dpi, then wait a command from the cookies dpi with the answer and the function return the cookies.
Yes, I understand. If you're curious just take a look at the chat command in bookmarks. There're three questions and answers for adding a bookmark! :-)
I have try to do the same that bookmarks dpi but the function used in it is void. I have try to understand ccc but i get it only superficialy.
The CCC is hard to understand from the code (don't waste your time). I'll try to take a look into it today and send you some code that does the trick, so you can hook your work to it. -- Cheers Jorge.-
On Sun, Apr 24, 2005 at 10:18:17AM +0200, Jorge Arellano Cid wrote:
Hi Diego,
On Sat, Apr 23, 2005 at 02:34:07PM +0200, Diego Sáenz wrote:
Hmm, what's the status of the cookies dpi?
It is almost done, but i need an answer to a big doubt before it.
how can a function wait(with a timeout if posible) until the cookies dpi send the answer to dillo after dillo have send to dpi cookies a get_cookies command?
Just let it block. Of course a non-blocking timeout or callback approach can be used (as with DNS or HTTP), but in this case the wait time is so short that it is not worth (it will be faster than bookmarks).
Unfortunately, after a long look into the code, I found out that there's no easy way to make it block (the natural way). Making it non-blocking is possible but non-trivial. I'll give it another try tomorrow... -- Cheers Jorge.-
Hi Diego, On Sun, Apr 24, 2005 at 09:18:40PM +0200, Jorge Arellano Cid wrote:
On Sun, Apr 24, 2005 at 10:18:17AM +0200, Jorge Arellano Cid wrote:
Hi Diego,
On Sat, Apr 23, 2005 at 02:34:07PM +0200, Diego Sáenz wrote:
Hmm, what's the status of the cookies dpi?
It is almost done, but i need an answer to a big doubt before it.
how can a function wait(with a timeout if posible) until the cookies dpi send the answer to dillo after dillo have send to dpi cookies a get_cookies command?
Just let it block. Of course a non-blocking timeout or callback approach can be used (as with DNS or HTTP), but in this case the wait time is so short that it is not worth (it will be faster than bookmarks).
Unfortunately, after a long look into the code, I found out that there's no easy way to make it block (the natural way).
Making it non-blocking is possible but non-trivial. I'll give it another try tomorrow...
Here's the patch! (I will send to you, not to the list). After a long day of coding a really hairy hack to make a non- blocking approach, It was almost working, but I didn't push it further because it was too ugly! :-) The good part is that after all that thought, a natural way to make it block came to me, so that's what the patch is. It has all the necessary stuff to bind your work. It comes with a custom cookies.dpi server example, the query is shown on stdout... Oh, it will be clear from the patch and its comments... It was a heavy context switch, now I'm back to the FLTK port. -- Cheers Jorge.-
Very thanks. I will try it now. DarkSpirit/Diego El Tue, 26 Apr 2005 11:16:54 +0200 Jorge Arellano Cid <jcid@dillo.org> escribio:
Hi Diego,
On Sun, Apr 24, 2005 at 09:18:40PM +0200, Jorge Arellano Cid wrote:
On Sun, Apr 24, 2005 at 10:18:17AM +0200, Jorge Arellano Cid wrote:
Hi Diego,
On Sat, Apr 23, 2005 at 02:34:07PM +0200, Diego Sáenz wrote:
Hmm, what's the status of the cookies dpi?
It is almost done, but i need an answer to a big doubt before it.
how can a function wait(with a timeout if posible) until the cookies dpi send the answer to dillo after dillo have send to dpi cookies a get_cookies command?
Just let it block. Of course a non-blocking timeout or callback approach can be used (as with DNS or HTTP), but in this case the wait time is so short that it is not worth (it will be faster than bookmarks).
Unfortunately, after a long look into the code, I found out that there's no easy way to make it block (the natural way).
Making it non-blocking is possible but non-trivial. I'll give it another try tomorrow...
Here's the patch! (I will send to you, not to the list).
After a long day of coding a really hairy hack to make a non- blocking approach, It was almost working, but I didn't push it further because it was too ugly! :-)
The good part is that after all that thought, a natural way to make it block came to me, so that's what the patch is. It has all the necessary stuff to bind your work.
It comes with a custom cookies.dpi server example, the query is shown on stdout... Oh, it will be clear from the patch and its comments...
It was a heavy context switch, now I'm back to the FLTK port.
-- Cheers Jorge.-
_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
participants (4)
-
Andreas Kemnade -
Diego Sáenz -
Jeremy Henty -
Jorge Arellano Cid