|
From: Raymond R. <ra...@ba...> - 2009-02-22 02:25:08
|
On Wed, Feb 18, 2009 at 10:21 PM, Raymond C. Rodgers < ra...@ba...> wrote: > Not yet, it's on my list for this weekend. I managed to solve some more > cookie problems about 10 days ago that I haven't submitted yet. Most > notably, the date parsing that I had been using seemed to suddenly stop > working, and Haiku has a simple to use date parser that is in a MIT license > that I'll probably selectively compile in for BeOS support, which means I'll > need to track down the correct file to re-appropriate. In the process of > tracking down another cookie related bug, I had to go digging through some > of the sources for the cache, and got to re-familiarize myself with it. The > problem is probably something simple like accidentally assigning the cache > token instead of comparing it or something like that... Nonetheless, I'll be > digging into that on Saturday. > Ok, the problem looks like it may be related to the gzip encoding support, which I think should be rewritten at some point. I noticed that with the encoding enabled, it added some extra characters to the beginning of the file transferred, but when the support was removed, the file was saved correctly. Right now, it's easier to comment out the line of code that adds the accept encoding header to the HTTP request than to go through and rewrite the gzip support, so I'm going to do that. As for the double notification about the page being completed... I haven't looked into it yet, but I suspect that the HTTP add-on is sending the initial notification, and then the SiteManager is turning around and sending the same or similar message. Raymond |