Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 08:13:10 2011 Capture.PNG
    icon2.gif   Re: Spurious characters in the searched string, posted by Stefan Ritt on Mon Sep 26 10:38:59 2011 
       icon2.gif   Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 11:16:19 2011 
          icon2.gif   Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 14:49:48 2011 
             icon5.gif   Re: Spurious characters in the searched string, posted by Phil Rubin on Mon Jan 3 19:11:08 2022 
Message ID: 67129     Entry time: Mon Sep 26 11:16:19 2011     In reply to: 67128     Reply to this: 67131
Icon: Reply  Author: Olivier Callot  Author Email: Olivier.Callot@cern.ch 
Category: Bug report  OS: Linux  ELOG Version: 2418 
Subject: Re: Spurious characters in the searched string 

Stefan Ritt wrote:

Olivier Callot wrote:

Hi,

We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.

Thanks in advance.

Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.

- Stefan 

 Well, It may be our implementation of re-routing web requests: The requested string in elog  is prefixed by %5E (^) and postfixed by %24 ($). But in my case, the '%' is again escaped as %25 so the prefix becomes %255E that is not understood by elog as being '^' ...

I will see with my experts in routing if this is something that can be fixed in our configuration. But when elog processes the input string, it should un-escape these characters and find back the '^', no?

ELOG V3.1.4-bcd7b50