Since elog 2.6.0 we cannot redirect our elog via apache2.

in apache2.conf we have (had for a long time):
Redirect permanent /elog http://elog.oursite.com/elog/
ProxyPass /elog/ http://elog.oursite.com:8080/

When visiting the url, this results in:
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elog/myelog/.

After testing we found that ELOG V2.6.0-beta2 works just fine.
2.6.0 stable crashes after visiting a redirected url.

Running on debian sarge

> > Since elog 2.6.0 we cannot redirect our elog via apache2.
> > 
> > in apache2.conf we have (had for a long time):
> > Redirect permanent /elog http://elog.oursite.com/elog/
> > ProxyPass /elog/ http://elog.oursite.com:8080/
> > 
> > When visiting the url, this results in:
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request GET /elog/myelog/.
> > 
> > After testing we found that ELOG V2.6.0-beta2 works just fine.
> > 2.6.0 stable crashes after visiting a redirected url.
> > 
> > Running on debian sarge
> 
> Have you tried 2.6.1. I released it just recently, so I don't know when it will be available for Debian.

No it doesn't work with 2.6.1. I hoped it would be fixed, but I should have reported it sooner.
I compiled 2.6.1 myself.
The original version was a debian package, after that, we compile elog ourselves and copy elogd manually over the old
version. Just to stay up-to-date.

> Have you checked that your "URL = xxx" statement in the config file is correct? I see above "myelog", while the
proxy passes requests to "elog".

I changed our urls, just to be safe.
myelog is a 'sublogbook', like forum here. http://elog.oursite.com/elog/myelog

We are running V2.6.0-beta2 and it runs fine, without any alterations to our config files.
All previous versions runned fine too.

update:
After further testing on a different server, it seems to be an issue with the proxy and the proxy_http modules in sarge.
after loading and unloading  proxy_http this is the error:
The proxy server received an invalid response from an upstream server.

Typing in a text for a new entry results in an error message, whenever
one forgets to fill in mandatory attributes (as it should happen !). However
after using the back button in this case (Using netscape 4.79) I made the
experience, that the text typed in gets lost. Other browsers like Mozilla
or IE do not have this problem. Any idea how this problem can be
avoided for netscape as well ?

I too am having problems getting the self register to work.   Can you 
attach a sample password file??   When I click the New user, nothing 
happens.  I do not get the screen that shows on this demo site.

Couple Wish List Items for the Self Register:

-allow the user to pick which type of log entries (which categories, etc) 
they would like to subscribe to and receive notifications on.   

-Option to use an existing LDAP database to authenticate users instead of 
maintaining a password file.

Ok I got the password file to finally work.  Once I created a blank 
passwd.txt I get the self register page to appear and create the account.  

Next problem.  Once I'm logged in, and I click logoout, I get an error 
saying 
the logout command now allowed ???  Same holds true for the config option 
while logged in.  


> I too am having problems getting the self register to work.   Can you 
> attach a sample password file??   When I click the New user, nothing 
> happens.  I do not get the screen that shows on this demo site.

Also having the ability to subscribe to notifications for one or more 
logbooks (if access is given - along with the ability to choose which 
categories, etc notifications are sent.


> Couple Wish List Items for the Self Register:
> 
> -allow the user to pick which type of log entries (which categories, etc) 
> they would like to subscribe to and receive notifications on.   
> 
> -Option to use an existing LDAP database to authenticate users instead of 
> maintaining a password file.

Stefan,

Just wanted to say, great job on this logbook.  I've been with you from the 
beginnning, and I must say it's evolved into an awesome tool.  Our IT dept 
lives by this logbook for change control mgmt, as well as a great way to 
keep everyone informed.   Not to mention what a great audit / reference 
tool it has become.   

Eric