Site URL not completed. Bad redirection ?

gerard breiner nginx-forum at
Fri Nov 2 21:50:08 UTC 2012

Hello Francis,

Francis Daly Wrote:
> On Wed, Oct 31, 2012 at 07:02:55AM -0400, gerard breiner wrote:
> Hi there,
> > curl -k -i as
> > curl -k -i 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/
> > --------------------------------
> So it redirects to /SOGo/. What happens when you do that manually?
>   curl -k -i

curl -k -i give :

HTTP/1.1 200 OK
Server: nginx/1.2.4
Date: Fri, 02 Nov 2012 21:09:16 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 2613
Connection: keep-alive

<?xml version="1.0" encoding="utf-8"?>
  <html xmlns="" lang="en">
	<meta content="0" name="hideFrame" />
	<meta content="SOGo Web Interface" name="description" />
	<meta content="SKYRIX Software AG/Inverse inc." name="author" />
	<meta content="stop" name="robots" />
	<meta content="@shiva 201210251146" name="build" />
	<link href="mailto:support at" rev="made" />
	<link rel="shortcut icon" type="image/x-icon"
href="https://sogo.mydomain/SOGo/WebServerResources/favicon.ico" />
	<link rel="stylesheet" type="text/css"
href="/SOGo.woa/WebServerResources/generic.css?lm=1351533524" />
	<link rel="stylesheet" type="text/css"
href="/SOGo.woa/WebServerResources/dtree.css?lm=1351283692" />
	<link rel="stylesheet" type="text/css"
href="/SOGo.woa/WebServerResources/SOGoRootPage.css?lm=1351611309" />
	<!--[if IE]><link rel="stylesheet" type="text/css"

      <body class="popup">
  <div id="loginScreen">
	  <img src="/SOGo.woa/WebServerResources/sogo-logo.png?lm=1351283693"
id="splash" alt="*" />
	<td id="loginCell" width="250">
	  <p>We've detected that your browser version is currently not supported on
this site. Our recommendation is to use Firefox. Click on the link below to
download the most current version of this browser.</p>
	  <p class="browser"><a href="">Download
Firefox</a> <img
alt="*" /></p>
	    <p>Alternatively, you can also use the following compatible
	  <p class="browser"><a href="">Download
Chrome</a> <img
alt="*" /></p>
          <p class="browser"><a
href="">Download Safari</a> <img
alt="*" valign="middle" /></p>

	  <div class="javascriptPopupBackground">
	  <div class="javascriptMessagePseudoWindow noJavascriptErrorMessage">
	    SOGo requires Javascript to run. Please make sure this option is
available and activated within your browser preferences.<br /><br /><a
href="" class="button">Retry</a>

> Probably it will redirect again, or else return some html. What you
> probably want to do is to manually step through the full login
> sequence
> until you see the specific problem. Then you can concentrate on that
> one request.
> (Also: that doesn't look like nginx 1.2.4. Are you sure that your test
> system is exactly what you expect it to be?)

I had downgrade nginx cause I wanted to see if I met the same issue with
both versions. I've upgrade it to 1.2.4.... 
> > From sogo.log
> > Oct 31 11:44:05 sogod [29392]: SOGoRootPage successful login for
> user
> > 'gbreiner' - expire = -1  grace = -1
> This is from a later time. So some other requests were involved here.
> > [31/Oct/2012:11:44:05 GMT] "POST /SOGoSOGoSOGo/connect HTTP/1.0" 200
> 27/62
> > 0.016 - - 4K
> > 
> > I think the "POST /SOGoSOGoSOGo/" is wrong ... 
> Can you see where that request came from? Probably it was the "action"
> of a html form within the response of a previous request. Maybe that
> will help show why SOGo is repeated here.

Before login there is GET /SOGoSOGo 
After login there is POST /SOGoSOGoSOGo/ 
> (That said, the HTTP 200 response suggests that the web server was
> happy
> with the request.)
> > (it is not the navigator because under apache2 it works very fine).
> Searching the web for "sogo and nginx" returns articles from people
> who
> claim to have it working.
> I suggest you step back and do exactly one thing at a time. With your
> original "location ^~ /SOGo" block, did it all work apart from the
> initial redirect? If not, fix that first.
> The SOGo installation guide mentions an apache config file, and says
> "The default configuration will use mod_proxy and mod_headers to relay
> requests to the sogod parent process. This is suitable for small to
> medium deployments.".
Make me puzzle ... For instance , templates will not be loaded without this 
 location /SOGo.woa/WebServerResources/ {
                         alias /usr/lib/GNUstep/SOGo/WebServerResources/;
> That suggests that your proxy_pass, proxy_redirect, and
> proxy_set_header
> directives may be enough.
> Good luck with it,

> 	f
> -- 
> Francis Daly        francis at
> _______________________________________________
> nginx mailing list
> nginx at

I 'm going to get a look at internet for getting a sogo configuration file
for nginx.
Yet my configuration come from internet and as it didn't work I tried this
and that and this and passed too much time working on this issue. If I
managed to get it work I'll come back here for sharing.

Thank you indeed Francis for your time and the quality of yours answers.

Best regards.


Posted at Nginx Forum:,232325,232465#msg-232465

More information about the nginx mailing list