Hi,
maybe some cached files in Chrome?
Martin

<div>-------- Původní zpráva --------</div><div>Od: Stéphane PERON 
<[email protected]> </div><div>Datum:14. 08. 2014  12:41  (GMT+01:00) 
</div><div>Komu: [email protected] </div><div>Předmět: Re: [SOGo] Problem while 
updating sogo </div><div>
</div>Hi,

I moved from an older chrome version to an earlier firefox version, and 
now it seems  to be ok ...

Stéphane

Le 14/08/2014 09:29, Stéphane PERON a écrit :
> Hi,
>
> After investigation, I found It comes from SOGo.conf when it is 
> configured behind a proxy ...
>
> SOGo works well when  I directly use on the sogo server like : 
> https://Mysogoserver/SOGo
>
> But it does not work anymore when I use an apache proxy server : Error 
> of url, no mail, no calendar,
>
> On my main apache server, I have a proxy defined like this :
>
> ProxyPass /SOGo http://192.168.200.93/SOGo interpolate
> ProxyPassReverse /SOGo  http://192.168.200.93/SOGo interpolate
>
> <Proxy http://192.168.200.93/SOGo>
>   RequestHeader set "x-webobjects-server-port" "443"
>   RequestHeader set "x-webobjects-server-name" "extranet.mycompany.com"
>   RequestHeader set "x-webobjects-server-url" 
> "https://extranet.mycompany.com/SOGo";
>   RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
>   RequestHeader set "x-webobjects-remote-host" "%{REMOTE_HOST}e 
> env=REMOTE_HOST"
>   AddDefaultCharset UTF-8
> #Require all granted
>   Order allow,deny
>   Allow from all
> </Proxy>
>
>
> And on the SOGo Server, my SOGo.conf say :
> <Proxy http://127.0.0.1:20000/SOGo>
>   RequestHeader set "x-webobjects-server-port" "443"
>   RequestHeader set "x-webobjects-server-name" "extranet.mycompany.com"
>   RequestHeader set "x-webobjects-server-url" 
> "https://extranet.mycompany.com";
>   RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
>   AddDefaultCharset UTF-8
>   Order allow,deny
>   Allow from all
> </Proxy>
>
>
> What could be the problem with this new version of SOGo and how could 
> I fix it ?
>
> Thanks a lot for your help !
>
> Stéphane
>
>
> Le 13/08/2014 12:53, Stéphane PERON a écrit :
>> Hi all,
>>
>> After updating sogo this morning, I got an error message when login ...
>> And the url displayed is now : /SOGo/soMYUSER
>>
>> So, It seems that I have lost a "/" between so and MYUSER ...
>>
>> How could I fix it ?
>>
>> Thanks a lot for your help
>>
>> Stéphane
>>
>>
>

-- 
[email protected]
https://inverse.ca/sogo/lists
-- 
[email protected]
https://inverse.ca/sogo/lists

Reply via email to