Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Bug Found, posted by nickc1 on Mon Jun 16 17:44:49 2003 
    icon2.gif   Re: Bug Found, posted by Stefan Ritt on Tue Jun 17 12:52:34 2003 
       icon2.gif   Re: Bug Found, posted by nickc1 on Fri Jun 20 10:40:43 2003 
          icon2.gif   Re: Bug Found, posted by Stefan Ritt on Mon Jun 23 10:53:55 2003 
Message ID: 377     Entry time: Fri Jun 20 10:40:43 2003     In reply to: 373     Reply to this: 378
Icon: Reply  Author: nickc1  Author Email: nick@nick.com 
Category: Bug report  OS: Linux  ELOG Version: 2.3.8 
Subject: Re: Bug Found 
> > Correct Way prior to 2.3.8
> > 
> > http://192.168.0.1:99/Provisioning%20Request/35
> > 
> > Broken way with new version
> > 
> > http://192.168.0.1:99/Provisioning Request/35
> 
> Exactly this problem has been fixed between 2.3.7 and 2.3.8, so can it be 
> that you mixed up these two versions? To be precise, the fix happend in 
> Revision 1.113 from 2003/06/04 08:17:35. So are you sure that you use a 
> version of elogd after that modification? I tried to reproduce your 
problem 
> with the official 2.3.8 version, but I got the correct result.

Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this 
upgrade, the only thing I kept was my own stylesheets and the config file.

One thing I just noticed is that if you dont have the URL statement set 
under global properties, some machines quote the hostname of the machine at 
which point this breaks the link. if you define the URL to the IP address 
the problem goes away.

However even without the URL setting undefined, it works for some people 
but not for others, I tried from 2 seperate machines and got 2 lots of 
results, so I suspect it might be DNS related somewhere along the lines.
ELOG V3.1.5-fe60aaf