Spurious "/.com" inserted into URL

(You can see this pretty-printed at
http://serverfault.com/questions/168098/nginx-just-started-inserting-spurious-coms-into-our-urls
)

I made some minor changes to our nginx config on Friday (deploying SSL
certs: adding a server listening on 443 with the appropriate settings
and adding a couple rewrite rules to forward certain requests to it) and
all of a sudden our URLs started getting extra "/.com"s inserted into
them. For example, clicking a link to http://domain.com/logout/ takes
the user to http://domain.com/logout/.com/. http://domain.com/register/
forwards to http://domain.com/.com/register/. This doesn’t happen with
a subdomain (e.g. http://production.domain.com/logout/ just works) and
it also doesn’t happen with https://domain.com/ (so right now, as a
workaround, the entire site is being served with https).

Our nginx serves static content and proxies dynamic requests to Apache,
which is pretty standard for Django. This had been working fine for
months; I have no idea why it stopped working. I can’t even be sure the
problem is at the nginx level, but that’s the only thing I changed, so
that’s where my attention has been.

Any help/suggestions would be greatly appreciated.

Here are the relevant config files (again, the link above has this
formatted nicely):

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,117878,117878#msg-117878

Hi, I’d suggest changing

  server {
    listen    80;
    server_name domain.com production.domain.com;
    root   /var/www/domain.com/;

to root /var/www/domain.com;

and re-check your regexes, but that’s just a newbie hint.


() ascii-rubanda kampajno - kontraŭ html-a retpoŝto
/\Â ascii ribbon campaign - against html e-mail

On Mon, Aug 09, 2010 at 07:12:11PM +0100, Nuno Magalhães wrote:

Hi, I’d suggest changing

server {
listen 80;
server_name domain.com production.domain.com;
root /var/www/domain.com/;

to root /var/www/domain.com;

No, the trailing slash in root can not do this.

and re-check your regexes, but that’s just a newbie hint.


Igor S.
http://sysoev.ru/en/

Thanks Igor, will do. However, logging that means disabling my
workaround on production, and I can’t really do that during the
day…but I’ll give it a shot tonight, when our users are mostly
asleep.

Igor S. Wrote:


Igor S.
http://sysoev.ru/en/


nginx mailing list
[email protected]
http://nginx.org/mailman/listinfo/nginx

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,117878,118014#msg-118014

On Mon, Aug 09, 2010 at 02:03:27PM -0400, desiato wrote:

forwards to http://domain.com/.com/register/. This doesn’t happen with
Any help/suggestions would be greatly appreciated.
Try to log $sent_http_location and $upstream_http_location to
see who sent wrong redirects.

* the English wiki - http://wiki.codemongers.com/Main

default_type  application/octet-stream;
keepalive_timeout  65;
    server  localhost:9001;
    listen      80;

            rewrite ^/(.*)  https://domain.com/$1 permanent;
            proxy_pass         http://django;
        }
    }

This configuration should rewritten as

     location / {
         try_files  $uri/index.html  $uri  @django;
     }

     location @django {
         proxy_set_header X-Forwarded-For 

$proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://django;
}

     location /register/ {
         rewrite ^/(.*)  https://domain.com/$1 permanent;
     }

     location /accounts/subscription/ {
         rewrite ^/(.*)  https://domain.com/$1 permanent;
     }
    ssl_certificate /etc/nginx/conf.d/full.crt;
        }

location / {
try_files $uri/index.html $uri @django;
}

     location @django {
         proxy_pass         http://django;
     }
location / {
    if (-f $request_filename/index.html) {
        rewrite (.*)    $1/index.html break;
    }
    if (!-f $request_filename) {
        proxy_pass         http://django;
    }
}

}
[/quote]


Igor S.
http://sysoev.ru/en/

Thanks, proxy_redirect off; seems to have done the trick. Really
weird behavior…

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,117878,118134#msg-118134

Hello!

On Mon, Aug 09, 2010 at 02:03:27PM -0400, desiato wrote:

forwards to http://domain.com/.com/register/. This doesn’t happen with
a subdomain (e.g. http://production.domain.com/logout/ just works) and
it also doesn’t happen with https://domain.com/ (so right now, as a
workaround, the entire site is being served with https).

I can’t say for sure as you stripped lots of details from your
report, but it sounds similar to the following issue (mostly in
Russian):

http://nginx.org/pipermail/nginx-ru/2010-February/032586.html

Try using “proxy_redirect off;” to see if it helps.

If it doesn’t - please provide debug log. See here for details:

http://nginx.org/en/docs/debugging_log.html

Maxim D.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs