2244 is now running, and indeed, the "Size" attribute works now. Thank you!

By now, I've installed 2244 and ran some rudimentary tests. So far, I was not able to reproduce the crash anymore. Looking good!

We use eLOG with IE. Once we turned on SSL, it is no longer possible to "Export to CSV" and save the output.

The error that we get is:

Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.

This is documented on Microsoft's site: http://support.microsoft.com/kb/316431

It is considered a feature with no fix. Basically the browser is honoring a request from the server which is "Pragma: no-cache". Problem can be reproduced in IE versions 6 through 8.
 

I see the same problem with IE. The knowledge base says that one should remove the "no-cache" statement from the header, but that has strange side effects: Assume you export a logbook to a CSV file, and a few days later you export it again, since many things changed. But you browser will in that case not retrieve the new logbook, but read the old CSV file from the cache. But the browser does not tell you this, so you see an old version of the logbok without knowing this, which can be dangerous. So I better leave the "no-cache" in the header. The workaroung is not to click on "Save" on the file download dialog, but on "Open". You see then the CSV data inside the browser and can copy/paste it into a notepad document, then save it. 

 Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet.   They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients".  So you see why I find it amusing.  I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin).  First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy.   Please let us know.

I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer. 

 Trust me, I don't want them getting old data either.. that would be a nightmare..

of course, the little voice at the back of my head (note, not IN the back of my head) has offered up this tidbit for you to consider.

Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.

The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

Hopefully there are no other side effects to this change.

 You can also try to use a different browser.

Soren