> > > > > 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!