Recently, I had issues with nginx placing the port number after redirects if the URL was missing the trailing slash (for example: https://example.com/thing
would redirect to https://example:8080/thing/
). So, I added the line for port_in_redirect off;
and that fixed the issue. However, it's now causing another issue. If the url is missing the trailing slash, it redirects to HTTP.
https://example.com/thing
will redirect to http://example/thing/
, which causes a failed request.
This is what my nginx.conf looks like:
#user nobody;
worker_processes 1;
#error_log logs/error.log;
#error_log logs/error.log notice;
error_log /var/log/error.log info;
#pid logs/nginx.pid;
events {
worker_connections 1024;
}
http {
include mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
log_format logstash_json '{ "@timestamp": "$time_iso8601", '
'"@fields": { '
'"remote_addr": "$remote_addr", '
'"remote_user": "$remote_user", '
'"request": "$request", '
'"status": "$status", '
'"body_bytes_sent": "$body_bytes_sent", '
'"request_time": "$request_time", '
'"request_method": "$request_method", '
'"http_referrer": "$http_referer", '
'"http_user_agent": "$http_user_agent" } }';
access_log /var/log/access.log logstash_json;
sendfile on;
#tcp_nopush on;
#keepalive_timeout 0;
keepalive_timeout 65;
#gzip on;
server {
listen 8080; # Port to listen on
server_name localhost; # Servername
client_max_body_size 0; # Max upload size
chunked_transfer_encoding on; # Support for chunked transfer (upload)
port_in_redirect off;
#charset koi8-r;
#access_log logs/host.access.log main;
location / {
root html;
index index.html index.htm;
}
#error_page 404 /404.html;
# redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
# proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}
# another virtual host using mix of IP-, name-, and port-based configuration
#
#server {
# listen 8000;
# listen somename:8080;
# server_name somename alias another.alias;
# location / {
# root html;
# index index.html index.htm;
# }
#}
# HTTPS server
#
#server {
# listen 443 ssl;
# server_name localhost;
# ssl_certificate cert.pem;
# ssl_certificate_key cert.key;
# ssl_session_cache shared:SSL:1m;
# ssl_session_timeout 5m;
# ssl_ciphers HIGH:!aNULL:!MD5;
# ssl_prefer_server_ciphers on;
# location / {
# root html;
# index index.html index.htm;
# }
#}
#include servers/*;
}
Best Answer
By default,
nginx
issues an absolute URL in the 3xx response, which includes the scheme used to connect to the server. Your server at port 8080 is connected to overhttp
, so that is the scheme that appears in the 3xx response.Since version 1.11.8,
nginx
can be configured to issue a relative URL instead, which removes the scheme and hostname from the URL.See this document for details.
If you are using an older version of
nginx
(and upgrading it is not an option) you might be able to override the default behaviour by using an explicitif...return
statement.Your existing configuration seems fairly simple:
There are a number of edge cases, so the solution can become quite complex, but something like this might work for you: