Actually I'm not very good in Apache server configuration.
On Fri, Apr 25, 2014 at 4:29 PM, Marcello Lorenzi <[email protected]>wrote: > Hi Max, > could this temporary behavior be related to the same IP address sent by the > Apache mod_proxy for each client requests? In fact for OM side the client > that sends the requests is the same source address, and if a client doens't > execute a correct logout the cookie is managed for client I think. > > Could it be a correct assumption? > > Thanks, > Marcello > > I guess so. // is not very good in URL > On Apr 8, 2014 4:47 PM, "Marcello Lorenzi" <[email protected]> wrote: > > > I added this access entries taken by the access_log of OM: > > > > 92.168.250.163 - - [08/Apr/2014:23:34:22 +0200] "GET /openmeetings// > > HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:34:33 +0200] "GET /openmeetings// > > HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:34:54 +0200] "GET > > /openmeetings//signout HTTP/1.1" 302 - > > 192.168.250.160 - - [08/Apr/2014:23:35:05 +0200] "GET > > /openmeetings/signin?1 HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:35:05 +0200] "GET > > /openmeetings//signin HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:37:20 +0200] "GET /openmeetings// > > HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:37:28 +0200] "GET /openmeetings// > > HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:44:42 +0200] "GET /openmeetings// > > HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:48:29 +0200] "GET /openmeetings// > > HTTP/1.1" 302 - > > 192.168.250.163 - - [08/Apr/2014:23:48:36 +0200] "GET /openmeetings/ > > HTTP/1.1" 302 - > > > > The issue seems to be the / present into the request. Could it be the "/" > > char present at the end of proxypass and proxypassreverse directives? > > > > Marcello > > > > ------------------------------ > > From: [email protected] > > To: [email protected] > > Subject: RE: OM 3.0 and Apache ProxyPass > > Date: Tue, 8 Apr 2014 22:36:58 +0000 > > > > Hi Maxim, > > on my configuration both the directives are present but I also configured > > ProxyPassPreserverHost to On and ProxyRequest set to Off. > > > > I don't understand the real issue on this configuration but all the > > request are redirected to http://<ipaddr>:5080/signin with a correct 404 > > HTTP error. > > > > Marcello > > > > ------------------------------ > > Date: Tue, 8 Apr 2014 16:32:59 -0600 > > Subject: Re: OM 3.0 and Apache ProxyPass > > From: [email protected] > > To: [email protected] > > > > I guess you need proxypass proxypassreverse. If I'm not mistaken both are > > necessary > > On Apr 8, 2014 4:30 PM, "Marcello Lorenzi" <[email protected]> wrote: > > > > Hi All, > > I have upgrade my Openmeetings instance from 2.2.0 to 3.0.0 version this > > evening but I noticed a strange behavior. My installation is composed by 2 > > Apache webservers balanced on port 80 by a Load balancer and into the > > configuration of each webserver I configured a proxypass directive to move > > all the content to a single OM instance listening on port 5080. > > > > During the first time the configuration works but after some hours I > > noticed that all the contents are redirect to /signin page, but the page > > isn't present on the OM instance because it works with /openmeetings/signin. > > > > Could this problem be related to proxypass and the JSESSIONID created by > > OM? > > > > Thanks, > > Marcello > > > > > > -- WBR Maxim aka solomax
