Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 14:49:48 2011
|
Olivier Callot wrote: |
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?
|
It turned out to be a setting of our re-routing of requests that re-escaped the '%'. Sorry for the noise. Cheers |
Re: Spurious characters in the searched string, posted by Phil Rubin on Mon Jan 3 19:11:08 2022
|
Hi,
Ten years later...this problem shows up in my installation behind Apache, affecting only drop-down menu searches. Test installations with elog serving itself do not show the problem, so I presume it has something to do with Apache configuration, re-routing, etc. Unfortunately, this thread did not provide any details of the solution.
The problem looks like this:
Type: %255ERoutine%2524
or, in the url:
https://servername/?Type=%25255ERoutine%252524
Removing 2525 from front and back of the url makes everything work.
The only rewrite entries in the configuration file(s) are:
## Rewrite rules
RewriteEngine On
#redirect non-SSL traffic to SSL site
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
Perhaps there's a rewrite rule that could be added to block the 2525? Something like:
RewriteCond %{QUERY_STRING} 2525
RewriteRule .* - [F,L]
I don't have a lot of experience configuring Apache, so any suggestions would be welcome.
Thanks.
Phil
Olivier Callot wrote: |
Olivier Callot wrote: |
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?
|
It turned out to be a setting of our re-routing of requests that re-escaped the '%'. Sorry for the noise. Cheers
|
|
Re: Spell check, posted by Stefan Ritt on Mon Nov 6 17:18:04 2006
|
David Egolf wrote: | Is there a spell check that can be implemented in Elog or any recommended add on spell check?
|
I personally use Mozilla Firefox 2.0 which has already a built in spell checker. For MS IE, you can use IESpell (http://www.iespell.com). |
Re: Spell check, posted by Fergus Lynch on Mon Nov 6 17:36:35 2006
|
David Egolf wrote: | Sorry if this has been asked.
Is there a spell check that can be implemented in Elog or any recommended add on spell check?
Thanks,
David Egolf |
I find that the Google spell checker works very well in IE6. |
Re: Specifying the size of am image attachment, posted by Stefan Ritt on Wed Apr 8 12:25:07 2009
|
Val Schmidt wrote: |
I'm curious, is it possible to specify (perhaps by default) the rendered size of an attached image. For example, I'd like all images uploaded to be scaled to 100% of the browser window size so a large image is not most off the screen. What I want is to specify the width="100" attribute of the <img /> tag, but it's not clear 1) how do to this for an attachment and 2) if it might be possible to do this in the config file for all img attachments.
|
When you use the ImageMagick package, attached images are scaled to a predefined size using the option "Thumbnail size = ...". See the documentation for that option for details. |
Re: Special characters in attribute names, posted by Stefan Ritt on Mon Nov 17 10:18:52 2008
|
Steve Williamson wrote: |
Hi
Thanks for elog - it's a brilliant piece of software. I'd looked all over for open source software to log/manage change requests before discovering elog; it's so flexible that I've been able to do everything I need with it.
However, I think that I've just discovered my first undocumented 'feature'. Attribute names containing punctuation characters (e.g. / and :) cause "Redirection limit for this URL exceeded" errors in Firefox 3.0.2 and corrupt the URL if they're used in a Quick Filter. I often use '/' in attribute names for brevity, e.g. "Old/New Versions" but hadn't used one in a Quick Filter before.
|
Quick answer: Don't use '/' in attribute names ;-) but I guess you were kind of afraid to get this answer.
Somehow longer answer: I tried to reproduce your problem with following configuration:
[demo]
Attributes = Author, Type, Subject, Old/New
Options Old/New = Old, New
Quick filter = Type, Old/New
But I was not successful. Everything worked fine using ELOG V2.7.5-2137. Can you please check with the above configuration and tell me exactly when the redirection problem occurs? Is it during filtering on already on creating a new entry?
|
Re: Special characters in attribute names, posted by Steve Williamson on Mon Nov 24 13:49:56 2008 
|
Stefan Ritt wrote: |
Steve Williamson wrote: |
Hi
Thanks for elog - it's a brilliant piece of software. I'd looked all over for open source software to log/manage change requests before discovering elog; it's so flexible that I've been able to do everything I need with it.
However, I think that I've just discovered my first undocumented 'feature'. Attribute names containing punctuation characters (e.g. / and :) cause "Redirection limit for this URL exceeded" errors in Firefox 3.0.2 and corrupt the URL if they're used in a Quick Filter. I often use '/' in attribute names for brevity, e.g. "Old/New Versions" but hadn't used one in a Quick Filter before.
|
Quick answer: Don't use '/' in attribute names ;-) but I guess you were kind of afraid to get this answer.
Somehow longer answer: I tried to reproduce your problem with following configuration:
[demo]
Attributes = Author, Type, Subject, Old/New
Options Old/New = Old, New
Quick filter = Type, Old/New
But I was not successful. Everything worked fine using ELOG V2.7.5-2137. Can you please check with the above configuration and tell me exactly when the redirection problem occurs? Is it during filtering on already on creating a new entry?
|
Thanks for the advice!
I've just had time to set up a test for this using both empty and populated logbooks (which don't have Hardware/Software in every entry as the field was added recently) and newly created logbooks (which have consistent attributes) and saw the problem on .
The control ("Hardware/Software") causing the problem has three options "Hardware Only", "Software Only" and "Both". The problem happens every time you click on the "-- Hardware/Software --" (i.e. All) option in the Quick Filter after having previously selected one (or more) of the options as a filter. This produces the error:
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
* This problem can sometimes be caused by disabling or refusing to accept cookies.
I ran elog with a trace (attached) which shows lots of:
select(1024, [5], NULL, NULL, {1, 0}) = 1 (in [5], left {1, 0})
recv(5, "GET /Change_Log/?Hardware%2FSoftware=_all_ HTTP/1.1\r\nHost: localhost:8080\r\nUser-"..., 100000, 0) = 619
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1323, ...}) = 0
time(NULL) = 1227528904
send(5, "HTTP/1.1 302 Found\r\nServer: ELOG HTTP 2.7.5-2130\r\nConnection: Keep-Alive\r\nKeep-A"..., 199, 0) = 199
send(5, "<html>redir</html>\r\n", 20, 0) = 20
messages after selecting "-- Hardware/Software --"
The only difference between today's test and last week's is that today the browser is on the local machine.
I also attach my (anonymised) elogd.cfg
Hope this helps
regards
Steve
|
Re: Special characters in attribute names, posted by Stefan Ritt on Mon Nov 24 17:53:23 2008
|
Thanks to your detailed description I could reproduce and fix the problem. Please download SVN revision #2144 and give it a try. |
|