ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66545
|
Wed Sep 16 16:37:35 2009 |
| Chuck Brost | Brost_chuck@solarturbines.com | Question | Windows | 2.7.6-2236 | Elog & SSL Export to CSV , Problem |
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.
|
66546
|
Wed Sep 16 23:54:12 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
Chuck Brost wrote: |
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. |
66547
|
Thu Sep 17 15:52:36 2009 |
| Holger Mundhahs | holger.mundhahs@vtg.com | Bug report | Windows | 2.7.7-2246 | Change / List Change doen't work anymore? | Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my .cfg file I've:
In the old ELOG version I've "RIB-Board" as text in the page and the link works well. But now there is the following code generated:
Is the syntax changed from 2.7.0 to 2.7.7? What's the correct syntax for 2.7.7?
Best regards
Holger |
66549
|
Thu Sep 17 18:31:44 2009 |
| Chuck Brost | Brost_chuck@solarturbines.com | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
Stefan Ritt wrote: |
Chuck Brost wrote: |
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. |
66550
|
Thu Sep 17 18:32:59 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.7-2246 | Re: Change / List Change doen't work anymore? |
Holger Mundhahs wrote: | Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my .cfg file I've:
In the old ELOG version I've "RIB-Board" as text in the page and the link works well. But now there is the following code generated:
Is the syntax changed from 2.7.0 to 2.7.7? What's the correct syntax for 2.7.7?
|
For security reasons (XSS or cross site scripting) , HTML code in attributes is not allowed by default. To turn it on (and if you know what you are doing), add following line to your configuration
Allow HTML = 1 |
66551
|
Thu Sep 17 18:44:52 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
Chuck Brost wrote: |
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. |
66552
|
Thu Sep 17 20:46:51 2009 |
| Chuck Brost | Brost_chuck@solarturbines.com | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
Stefan Ritt wrote: |
Chuck Brost wrote: |
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.
|
66571
|
Mon Nov 2 21:23:38 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 | I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
Thanks,
David |
|