Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   redirect errors via apache2, posted by djek on Mon Jan 23 10:30:51 2006 
    icon2.gif   Re: redirect errors via apache2, posted by Stefan Ritt on Mon Jan 23 10:57:45 2006 
       icon2.gif   Re: redirect errors via apache2, posted by djek on Mon Jan 23 11:18:48 2006 
Message ID: 1618     Entry time: Mon Jan 23 10:57:45 2006     In reply to: 1617     Reply to this: 1619
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS: Linux  ELOG Version: 2.6.1  
Subject: Re: redirect errors via apache2 
> 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. 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".
ELOG V3.1.5-2eba886