> > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > 
> > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > Is is possible the corporate elog server is running behind apache or in some
> > other proxy config while the one you are having issues with is being connected
> > to directly by chrome?
>
> It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> URL to Google Chrome developers to see if it's a bug in the browser or not.

I just brought up the current head release of elog, and the problem is fixed. Looks like it 
was some sort of cookie issue IIRC the log entry.

So build a new elogd and you should be all set.

- rouilj

> > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > 
> > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > Is is possible the corporate elog server is running behind apache or in some
> > > other proxy config while the one you are having issues with is being connected
> > > to directly by chrome?
> >
> > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > URL to Google Chrome developers to see if it's a bug in the browser or not.
> 
> I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> was some sort of cookie issue IIRC the log entry.
> 
> So build a new elogd and you should be all set.
> 
> - rouilj

Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.

> > > > > Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.
> > > > 
> > > > I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
> > > > Is is possible the corporate elog server is running behind apache or in some
> > > > other proxy config while the one you are having issues with is being connected
> > > > to directly by chrome?
> > >
> > > It's good to know someone else has the issue, at least.  I'd like to find a publicly available elog server so 
> > > that the elog developers could recreate the issue and thusly fix the issue.  Or at the very least send the broken 
> > > URL to Google Chrome developers to see if it's a bug in the browser or not.
> > 
> > I just brought up the current head release of elog, and the problem is fixed. Looks like it 
> > was some sort of cookie issue IIRC the log entry.
> > 
> > So build a new elogd and you should be all set.
> > 
> > - rouilj
> 
> Thanks.  I'll have to wait for someone else to build the win32 binary, as I'm not set up to compile it myself.

I installed the latest Windows build (didn't realize I missed a build in November), and it now works in Chrome.  Thanks!

> Hello,
> 
> is it possible to have an guest account together with a global password file?
> 
> I tried to put the password file statement into the global section of
> elogd.cfg. But in this case every user must login and it is not possible to
> have a read only guest account. 
> But if I put the password file statemnet into the logbook sections, it is
> possible to access the logbooks in read-only mode without logging in. The
> drawback of this solution is, that you have to login into every logbook
> seperately.
> 
> Bertram

Right, guest access is not possible with a global password file. This comes from
the fact that people wish to protect their logbook selection page. What I can do
is add another flag "protect selection page = 0 | 1". If "0", the logbook
selection page can be seen without logging in. Is that what yo want?

- Stefan

> > Hello,
> > 
> > is it possible to have an guest account together with a global password file?
> > 
> > I tried to put the password file statement into the global section of
> > elogd.cfg. But in this case every user must login and it is not possible to
> > have a read only guest account. 
> > But if I put the password file statemnet into the logbook sections, it is
> > possible to access the logbooks in read-only mode without logging in. The
> > drawback of this solution is, that you have to login into every logbook
> > seperately.
> > 
> > Bertram
> 
> Right, guest access is not possible with a global password file. This comes from
> the fact that people wish to protect their logbook selection page. What I can do
> is add another flag "protect selection page = 0 | 1". If "0", the logbook
> selection page can be seen without logging in. Is that what yo want?
> 
> - Stefan
Yes, that is what I want.
Bertram

> Yes, that is what I want.

I implemented a switch "protect selection page" in revision 1.318, which can be
obtained at http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.318. If this
switch is not set to "1", the selection page can be seen without having to log in.

> > Yes, that is what I want.
> 
> I implemented a switch "protect selection page" in revision 1.318, which can be
> obtained at http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.318. If this
> switch is not set to "1", the selection page can be seen without having to log in.

Stefan,
thank you for the fast implementation of this feature. I compiled the new revision and
it worked as expected.

Kind regards,
Bertram

You would have to access the raw elgo database files (which are pure ASCII files) and write some script which goes through all files and changes the URLs. 

Stefan