Nginx add trailing slash with wrong port

nginx rewrites :

http://localhost:8081/files

to :

http://localhost:81/files/ # wrong port !

while apache rewrites :

http://localhost:8082/files

to

http://localhost:8082/files/

is it possible to configure nginx to behave like apache ?

/etc/nginx/conf.d/test.conf :

server {
listen 81;
location /files {
alias /home/luc2/files;
autoindex on;
}
}

/etc/httpd/conf.d/test.conf :

<VirtualHost *:82>
Alias /files /home/luc2/files
<Directory /home/luc2/files>
Options indexes
Allow from all

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

A listen to port 81 should not invoke a response from 8081, check to see
who
is listening on 8081.

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

On May 24, 2014 2:53 PM, “luc2” [email protected] wrote:

server {
Alias /files /home/luc2/files
<Directory /home/luc2/files>
Options indexes
Allow from all

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


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

Aliases (and any other configurable sharing a name with something in
Apache) generally don’t do the same thing as in Apache. Just use “root”
inside the location block.

Dustin

On Sat, May 24, 2014 at 02:53:21PM -0400, luc2 wrote:

Hi there,

nginx rewrites :

http://localhost:8081/files

to :

http://localhost:81/files/ # wrong port !

is it possible to configure nginx to behave like apache ?

No.

If your use case is restricted to one of the two mentioned below, then
you might be able to fake it adequately.

nginx does not have a config option to do what you seem to want, which
is “use the incoming http Host: header value in any generated Location:
response header”.

Using “port_in_redirect”, you can auto-include either no port at all,
or whichever port the connection actually came to nginx on (which will
be one of the ports listed or implied in the “listen” directives).

If you don’t want to patch the code to add your use case, then

  • if you have a fixed list of redirections, you could add a number of
    locations of the form

    location = /dir1 { return 301 $scheme://$http_host/dir1/; }

  • or if there is exactly one host/port that you will always want to
    return
    (e.g. server:8081), then you could

    port_in_redirect off;
    server_name_in_redirect on;
    server_name server:8081;

But otherwise, I don’t think it can be done.

f

Francis D. [email protected]

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