[quote="Stefan Ritt"][quote="Heiko Scheit"]The 'reverse sort' option does not work for quick filter searches. 
In the
URL there is always written 'reverse=0'.  For normal 'Find' it works OK.[/quote]

I don't understand the problem. If I take the example elogd.cfg from the distribution, it sorts in reverse
order, since the file contains [i]Reverse sort=1[/i]. If I apply a quick filter, the result is still sorted in
reverse order (entry ID from high to low). If I set [i]Reverse sort=0[/i], the even after applying a quick
filter, the entries are sorted with their ID from low to high. Applying a quick filter should not put a
[i]reverse=0[/i] into the URL, so it's strange to me where this comes from. Can you try to reproduce the problem
with the demo elogd.cfg?[/quote]

I played with the quick filter settings somewhat.  Here is what I get.
I can't really make sense of it, but maybe you can figure out what
happens.  Below, the first line always contains the 'Quick filter'
config setting.  The lines below show the URL after searching with the
quick filter for the 1st, 2nd,... attribute listed in the quick filter
setting.  (The common base of the URL was removed.  Shown is
everything after the last '/'.)  Each 'quick search' was started from
the 'List' or 'Back' page, i.e. the URL ended with a '/'.

As you can see below the result depends on the number and on the order
(!) of the attributes.  Only a few give the desired result (marked
with # OK).  Incidentally the option 'Date, Something' works fine,
which is the combination found in the demo config file.  :)

Quick filter            = Subject, Date, Login
?Subject=sd&Login=           # OK
?last=1&&reverse=0
?Login=sdf&reverse=0

Quick filter            = Subject, Login, Date
?Subject=scd&reverse=0
?Login=sdf&reverse=0
?last=1&reverse=0

Quick filter            = Date, Subject, Login
?last=1&&reverse=0
?Subject=sd&Login=           # OK
?Login=sd&reverse=0

Quick filter            = Subject, Date
?Subject=sd                  # OK
?last=1&reverse=0

Quick filter            = Date, Subject
?last=1&Subject=             # OK
?Subject=ddsd                # OK

Quick filter            = Login, Date
?Login=sch                   # OK
?last=31&reverse=0

Quick filter            = Subject, Login
?Subject=dsd&Login=          # OK
?Login=sd&reverse=0

Quick filter            = Login, Subject
?Login=sd&Subject=           # OK
?Subject=sd&reverse=0

?cmd=Activate&new_user_name=test1&new_full_name=Test1

http://my.ho.st/?cmd=Activate&new_user_name=test1&new_full_name=Test1

http://my.ho.st/myLogBook/?cmd=Activate&new_user_name=test1&new_full_name=Test1

The 'elog' utility for commandline submission used wrong 'Host:' in POST header.
The host listed after 'Host:' should be the host where the server runs, not the 
localhost (see patch below).

$ diff -u elog.c_20050711  elog.c
--- elog.c_20050711     Mon Jul 11 18:54:20 2005
+++ elog.c      Mon Jul 11 18:55:31 2005
@@ -421,7 +421,7 @@
       sprintf(request + strlen(request), "%s/%d?cmd=download", experiment, message_id);
    strcat(request, " HTTP/1.0\r\n");
 
-   sprintf(request + strlen(request), "Host: %s\r\n", host_name);
+   sprintf(request + strlen(request), "Host: %s\r\n", host);
    sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
 
    first = 1;
@@ -872,7 +872,7 @@
    strcat(request, " HTTP/1.0\r\n");
 
    sprintf(request + strlen(request), "Content-Type: multipart/form-data; boundary=%s\r\n", boundary);
-   sprintf(request + strlen(request), "Host: %s\r\n", host_name);
+   sprintf(request + strlen(request), "Host: %s\r\n", host);
    sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
    sprintf(request + strlen(request), "Content-Length: %d\r\n", content_length);

   An 'encoded-word' may not be more than 75 characters long, including
   'charset', 'encoding', 'encoded-text', and delimiters.  If it is
   desirable to encode more text than will fit in an 'encoded-word' of
   75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may
   be used.