Hello Francis, Francis Daly Wrote: ------------------------------------------------------- > On Wed, Oct 31, 2012 at 07:02:55AM -0400, gerard breiner wrote: > > Hi there, > > > curl -k -i https://127.0.0.1 as > > curl -k -i https://sogo.mydomain.fr give: > > ------------------------------ > > HTTP/1.1 302 Found > > Server: nginx/0.7.67 >by gerard breiner - Nginx Mailing List - English
Hello, curl -k -i https://127.0.0.1 as curl -k -i https://sogo.mydomain.fr give: ------------------------------ HTTP/1.1 302 Found Server: nginx/0.7.67 Date: Wed, 31 Oct 2012 10:37:27 GMT Content-Type: text/plain; charset=utf-8 Connection: keep-alive content-length: 0 location: /SOGo/ -------------------------------- From sogo.log Oct 31 11:44:05 sogod [29392]: SOGoRootPage succesby gerard breiner - Nginx Mailing List - English
Hello Francis, I replaced : location ^~/SOGo { proxy_pass http://127.0.0.1:20000; proxy_redirect http://127.0.0.1:20000 default; By location /SOGo { proxy_pass http://127.0.0.1:20000/; } And I get the URL I expected https://sogo.mydomain/SOGo but when I want authenticate to I get the message : "You can not authenticate because the witnesses (cookies) on your broby gerard breiner - Nginx Mailing List - English
Hello, I'm trying to replace apache2 by nginx. So far my platform debian squeeze + Apache2 + sogo 2.0.2 works very fine. However I decided to replace apache2 by nginx 1.2.4-1. It works too but it seems there is a redirection that doesn't work. My url : https://sogo.mydomain give a page error 403 forbidden. I have to complete the url with /SOGo so that I get the login. Here is the error.log oby gerard breiner - Nginx Mailing List - English
Hello, I'm trying to configure nginx for using in the context sogo webmail. I meet a problem I'm going to submit.... Best regards. GĂ©rardby gerard breiner - New Member Introductions