Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 204 of 801  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1490   Fri Oct 28 12:16:38 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0beta5Re: Display last page by default

Yoshio Imai wrote:
Is it possible to configure the logbook so that "List" takes me to the last page instead?


Reverse sort = 1
  1492   Fri Oct 28 13:05:26 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0beta5Re: Display last page by default

Yoshio Imai wrote:
We would like to see the entries in normal order, but the last of the pages as "start page". Is it possible to configure this?


Start page = 0?cmd=last

Well, I guess this is not what you want either, correct? You would like to see the listing page with ~20 entries. The first one you can access easily via "<logbook>/page1", but the number of the last page varies over time. I would have to add a new functionality like "<lobook>/page_last", which automatically gets converted into the correct page number. I will put this on my wishlist.
  1494   Fri Oct 28 13:14:19 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0beta5Re: Display last page by default

Yoshio Imai wrote:
We would like to see the entries in normal order, but the last of the pages as "start page". Is it possible to configure this?


What about

Start page = last10

This shows always the last 10 entries. If you want to see more, you can click on the new menu entry "Last 20 entries" etc.
  1496   Fri Oct 28 20:36:55 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0beta5Re: Display last page by default
Ok, I implemented the last page display per default in revision 1538. If "reverse sort = 0" the last page is shown and if "reverse sort = 1" the first page is shown by default. This way one always sees the page with the latest entries. I hope this accomodates everybody. If not, please complain and I could make it a switch (yet another option Crying ).
  1497   Fri Oct 28 23:45:33 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.0beta2Re: Conditional hiding of attributes in list view

Yoshio Imai wrote:
I have also found one possible problem, maybe it's already solved in the
newest version: We have set up the elog under an stunnel, but the elog
server also responds to the original port (i.e. 80), displaying the logbook
selection page and from there even the login screen. Only after logging in
the elog server redirects the client browser to the https-page defined with
the URL-statement of the config file. The whole thing seems like an unwanted
behaviour, but could you change it so that it either doesn't respond on the
wrong URL at all, or at least redirects to the secured URL before presenting
the login window, so that we transfer the passwords encrypted?


I implemented that in revision 1540. On the logbook selection page, the links to the individual logbooks honor the "URL = ..." statement from the config file, and thus you get redirected via "https://...". More is unfortunately not possible. If elogd gets contacted the first time, it is impossible to figure out by elogd under which URL it got contacted, and therefore it cannot distinguish between secure and insecure connections. The only way is to switch off port 80 by a firewall and only allow "https://..." connections from outside.
  1502   Mon Nov 7 09:16:47 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: Problems with ELOG and Internet Explorer

Elaine Cristina Franchini dos Anjos wrote:
We are facing a problem when using the Internet Explorer browser to edit
logbooks entries. The error occurs when we use the preview option.

After this, the connection becomes slow to display the preview and returns
"Server Not Found - Page cannot be displayed" or "Internal Server error" as result.
If we try to turn back to the edit page the browser retuns
"This page has been expired".

It happens at any time even we edit simple entries in Internet Explorer,
but never occurs in other browsers.

Software versions that are running :

Elog version 2.6.0-beta
Fedora Core release 1 (Yarrow)
Apache/2.0.54 (Unix) mod_ssl/2.0.54 OpenSSL/0.9.7g
(Elog is running under apache proxy)

Is there any bug report about this or there is something else
that I need to configure ?


I tried on this forum with Internet Explorer 6.0 and could not reproduce the problem, and I never heared anybody else mentioning this problem. Can you reproduce the problem on the forum?
  1503   Mon Nov 7 09:25:59 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.0beta5Re: ELOG v2.6.0-beta5 (Windows) crashes while using " Forgot password?"

Edmundo T Rodriguez wrote:
The following ELOG behavior seems to be like a bug ...

-> Anybody click on "Forgot password?" in the login screen, to have the system
send him the forgotten password, and after a little while trying, (possibly doing
resolution) the ELOG application crashes.

The ELOG service have to registered again.

The SMPT host may not be right, but ELOG should not crash just for that.

It should says something like "Can not find SMTP server", etc.


I have fixed that in SVN revision 1541.
  1505   Tue Nov 8 08:17:22 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: Problems with ELOG and Internet Explorer

Elaine Cristina Franchini dos Anjos wrote:
I edited and used preview many times and the ELOG worked fine without errors in IE. So, I think my problem is something configured in the proxy or https that Internet Explorer doesn't work very well in this circumstance.


Have a look at your URL = ... statement in elogd.cfg
It should probably read
URL = https://antares.ccuec.unicamp.br:9696

ELOG uses redirection internally. To determine it's own address, it uses the URL statement. If you use Apache as an proxy together with https, you have to specify the URL under which you usually access ELOG from outside. If this is wrong, ELOG might try to redirect to http:// or something which might not be possible.

A good way to debug this is to run ELOG with the -v flag and carefully watch the HTTP traffic. You will see Location: ... statements which redirect the browser, then the browser will access the redirected URL (if it's correct), or you will see nothing (in case the browser tries to access a non-existing URL).
ELOG V3.1.5-3fb85fa6