Hi again,

So I think I have found the reason why dillo cannot log into gmail and the problem is general enough to affect other websites.
The gmail website is using Twarte Certificate Authority for https certificates. I did not configure the https DPI to recognize Twarte (I don't know if it is even possible). So each time I go to the gmail login page, dillo pops up the warning dialog box asking the user whether or not to proceed with an unrecognized certificate. For each image and element that are downloaded with https from the gmail login page, a new https DPI process gets forked and causes the warning dialog box to pop up again. There are too many dialog boxes that get poped up and some of them get dropped and are not shown to the user. As a result there are several https DPI processes hanging around still waiting for an answer from the user. One of those https DPI processes is the one that is sending the HTTP POST request to login to gmail.

Best Regards
Richard Ta-Min

On 1/13/06, Richard <judicator3@gmail.com> wrote:
Hello

Thanks for the quick response.

Most probably. Disable javascript in Firefox and try to log in.
That's a good starting point.

Yes I tried that with firefox and JS disabled. Gmail is smart enough to send you a version of the HTML page that does not require JS and you can log in. So JS is probably not the issue why I cannot login with dillo. I had some more time yesterday to look into the problem. It seems for whatever reason, dillo is not sending the form's POST HTTP request when I click on the "Sign In" button of the login form. I'll look into the problem. If it is truly a bug I'll let you guys know.

  Good. Is JS your expertise area?

Not exactly. I am working of some other project right now, but later I may have the necessary time to devote in learning. I'll keep the JS issue in the back of my mind.
 
Best regards
Richard Ta-Min