ELOG Forum

error when searching for POST

Other

V2.5.9-2

is this an elog bug?
calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elogs/Linux Demo/.

Reason: Error reading from remote server

--------------------------------------------------------------------------------

Apache/2.0.46 (Red Hat) Server at midas.psi.ch Port 80

doing the same thing on my elog installation (ELOG V2.5.9-2) gives the error

Die Seite kann nicht angezeigt werden.
Die gewünschte Seite ist zurzeit nicht verfügbar. Möglicherweise sind technische Schwierigkeiten aufgetreten oder Sie sollten die Browsereinstellungen überprüfen.

--------------------------------------------------------------------------------

Versuchen Sie Folgendes:

... (some text skipped, guenter)

Fehler: Server oder DNS kann nicht gefunden werden
Internet Explorer

if if dont type all letters in uppercase no problem occurs

thanks
guneter

1426

Wed Oct 5 13:07:51 2005

Re: error when searching for POST

Guenter Nowak wrote:

calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error

Proxy Error

This bug has been fixed in the current CVS version.

1744

Fri Mar 3 16:48:01 2006

Alexandre Gauthier

supernaut@underwares.org

Makefile patch for OS X 10.4

Mac OSX

SVN 1668

Hello,

I had trouble compiling elog on Mac OS X 10.4, and so, I hacked the makefile around...

I had to remove the -lutil flag that was passed to ld, for some reason. My guess is that it is not needed anymore with OS X 10.4... Also, the current install section of the makefile crapped out when using /usr/bin/install, I had to use install from gnu fileutils, which I installed through fink, which took precedence in my path... (/sw/bin/install), since bsd fileutil doesn't like the -D option.

For some reason, the paths to "install" in the makefile are either defined by the $(INSTALL) variable, or called directly. This seems not to be very consistent... In any case, I just changed it to use "install", no matter where it was in my path.

I'm currently hacking up something more elegant soon enough...

Also, I noticed that the binary produced was inconsistent and sluggish with the default wild CFLAGs, so I brought them back to something a bit more casual for Darwin. I used -Os because that's what Apple uses to build most OS X software. I also use -Os in my blackdog builds (which is an embedded PowerPC device) since space and memory *does* matters.

Well, here's the patch. I doubt it will be useful to anyone except for those who have gnu fileutils installed through fink, in their paths, and find themselves unable to build elog on OS X.

>    If you have only one entry in the logbook and have it set up in threaded 
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
> of the entry or the number of the entry to see it, it does not allow you 
> to.  If there is more than one entry, it works fine.  

Ok, has been fixed. Will come in 2.0.5

>    Also I wanted to make a submit page from where you could either go back 
> to the logbook which you just entered a message for or type a new entry for 
> that logbook.  First of all, is there a way to have only one file called 
> submitpage.html in which I can define this for all logbooks or do i need it 
> for ever logbook.  And also, is there a way I can even set a link that will 
> allow to create a new entry.  I tried: 
>     <a href="demo/?cmd=new">Enter</a> another message<p>
> 
> but for some reason it does not work.  Is there a way to implement this?

The documentation was wrong about that which has been corrected. The proper 
file contents should be

<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message

This way one only needs one file for all logbooks.

>    If you have only one entry in the logbook and have it set up in threaded 
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
> of the entry or the number of the entry to see it, it does not allow you 
> to.  If there is more than one entry, it works fine.  

Ok, has been fixed. Will come in 2.0.5

>    Also I wanted to make a submit page from where you could either go back 
> to the logbook which you just entered a message for or type a new entry for 
> that logbook.  First of all, is there a way to have only one file called 
> submitpage.html in which I can define this for all logbooks or do i need it 
> for ever logbook.  And also, is there a way I can even set a link that will 
> allow to create a new entry.  I tried: 
>     <a href="demo/?cmd=new">Enter</a> another message<p>
> 
> but for some reason it does not work.  Is there a way to implement this?

The documentation was wrong about that which has been corrected. The proper 
file contents should be

<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message

This way one only needs one file for all logbooks.

>    If you have only one entry in the logbook and have it set up in threaded 
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
> of the entry or the number of the entry to see it, it does not allow you 
> to.  If there is more than one entry, it works fine.  

Ok, has been fixed. Will come in 2.0.5

>    Also I wanted to make a submit page from where you could either go back 
> to the logbook which you just entered a message for or type a new entry for 
> that logbook.  First of all, is there a way to have only one file called 
> submitpage.html in which I can define this for all logbooks or do i need it 
> for ever logbook.  And also, is there a way I can even set a link that will 
> allow to create a new entry.  I tried: 
>     <a href="demo/?cmd=new">Enter</a> another message<p>
> 
> but for some reason it does not work.  Is there a way to implement this?

The documentation was wrong about that which has been corrected. The proper 
file contents should be

<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message

This way one only needs one file for all logbooks.