Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   HTML 4.1 transitional validation fails, posted by Emiliano Gabrielli on Mon Feb 7 18:55:02 2005 
    icon2.gif   Re: HTML 4.1 transitional validation fails, posted by Stefan Ritt on Mon Feb 7 20:13:28 2005 
       icon2.gif   Re: HTML 4.1 transitional validation fails, posted by Emiliano Gabrielli on Thu Feb 24 11:23:44 2005 
          icon4.gif   Re: HTML 4.1 transitional validation fails, posted by Emiliano Gabrielli on Thu Feb 24 12:44:29 2005 
          icon4.gif   Re: HTML 4.1 transitional validation fails, posted by Emiliano Gabrielli on Thu Feb 24 12:45:02 2005 
             icon2.gif   Re: HTML 4.1 transitional validation fails, posted by Stefan Ritt on Wed Mar 2 17:31:33 2005 
    icon4.gif   Re: HTML 4.1 transitional validation fails, posted by Emiliano Gabrielli on Tue Feb 8 13:11:30 2005 
       icon2.gif   Re: HTML 4.1 transitional validation fails, posted by Stefan Ritt on Sat Feb 12 17:40:55 2005 
    icon4.gif   Re: HTML 4.1 transitional validation fails, posted by Emiliano Gabrielli on Thu Mar 24 13:21:28 2005 
       icon2.gif   Re: HTML 4.1 transitional validation fails, posted by Stefan Ritt on Thu Mar 24 13:59:06 2005 
Message ID: 968     Entry time: Wed Mar 2 17:31:33 2005     In reply to: 962
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS: All  ELOG Version: r. 1.571 
Subject: Re: HTML 4.1 transitional validation fails 
> > I tried to substitute avery occurrence of hard coded "&" with "&" but it does
> > not do the job at all ... infact the first time the HTML code is ok, but
> > following a link let the browser to automatically decode html entities .. and
> > everything turns wrong again ... maybe the encoding should be done in
> > printing-to-the-browser-time ..

That won't help, since the 'Start page = ...' string is used for redirection (outside
of any HTML). The '&' thing should only occur inside the HMTL text.

I changed elogd.c to encode things properly, but I'm not sure if I covered all
occurences. Can you try release 1.576 if it works correctly?
ELOG V3.1.5-3fb85fa6