|
From: Raymond R. <ra...@ba...> - 2011-02-06 21:52:17
|
Hi all, I just want to take a moment to report on my latest tweak(s) to the HTTP add-on. Mark has mentioned on a couple of occasions that the broadcasts that the HTML parser sometimes receives doesn't contain the content's MIME type, in particular when loading the page a second time within any particular Themis session. Due to the nature of the issue, he thought it might be an issue with the cache system and asked me to investigate it. You'll probably guess correctly, because of the email subject, that the problem was actually in HTTP. Basically, the HTTP add-on was only adding the mime type to the broadcasts when the page wasn't found in cache or the server returned an updated version of the content. (A 200 level HTTP response rather than a 304 Not Modified response.) I think I deliberately did this, years ago, because the content type must not have changed if the server is returning a not modified response. Nonetheless, I didn't foresee that this would add further complications to other parts of the app, even though it would be possible to obtain the appropriate information directly from the cache system. So, I'm now including the MIME type in just about all "loading progress" broadcasts from HTTP, which should get the HTML parser working properly. My apologies for earlier my earlier weirdness... ;-) Raymond -- Raymond Rodgers http://www.badlucksoft.com/ http://anevilgeni.us/ |