Rewrite "https://files.mydomain.com/files" to "https://files.mydomain.com"

huangapple
go评论80阅读模式
英文:

Rewrite "https://files.mydomain.com/files" to "https://files.mydomain.com"

问题

  1. location ^~ /files {
  2.     rewrite ^/files/?(.*)$ https://files.mydomain.com/$1 permanent;
  3.     proxy_pass http://localhost:89/files;
  4. }
英文:

Currently, I am able to visit: https://files.mydomain.com/files. Even if I go to https://files.mydomain.com, it will redirect automatically to https://files.mydomain.com/files successfully.

Instead, I would like for NGINX to automatically rewrite https://files.mydomain.com/files -> https://files.mydomain.com

My current NGINX code:

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-properties -->

  1. http {
  3.     server {
  4.         
  5.             listen       80;
  6.             server_name  localhost;
  7.             return 301 https://$host$request_uri;
  8.     }
  10.     server {
  12.             listen       80;
  13.             server_name  files.mydomain.com;
  14.             location / {
  15.                 return 301 https://files.mydomain.com$request_uri;
  16.         }
  17.     }
  19.     server {
  20.             listen 443 ssl http2; 
  21.             listen [::]:443 ssl http2;
  22.             server_name  files.mydomain.com;
  23.             client_max_body_size 0;
  24.             location / {
  25.                 return 301 https://$host/files;
  26.             } 
  27.             location /files {
  28.                 proxy_pass http://localhost:89;
  29.             }
  30.     }
  32.     #Root Domain
  33.     server {
  34.             listen 443 ssl http2; 
  35.             listen [::]:443 ssl http2;
  36.             server_name_in_redirect off;
  37.             server_name  www.mydomain.com mydomain.com;
  38.             log_not_found off;
  40.         location / {
  41.             root   /inetpub/wwwroot;
  42.             index  index.html index.htm;
  43.         }
  44.     }
  45. }

<!-- end snippet -->

My best attempt:
Unfortunately, it just takes me to the "Welcome to NGINX" webpage when I visit:
https://files.mydomain.com

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-properties -->

  1. http {
  3.     server {
  4.         
  5.             listen       80;
  6.             server_name  localhost;
  7.             return 301 https://$host$request_uri;
  8.     }
  10.     server {
  12.             listen       80;
  13.             server_name  files.mydomain.com;
  14.             location / {
  15.                 return 301 https://files.mydomain.com$request_uri;
  16.         }
  17.     }
  19.     server {
  20.             listen 443 ssl http2; 
  21.             listen [::]:443 ssl http2;
  22.             server_name  files.mydomain.com;
  23.             client_max_body_size 0;
  24.             location ^~ /files {
  25.                 rewrite ^/files/?(.*)$ https://files.mydomain.com/$1 permanent;
  26.                 proxy_pass http://localhost:89/files;
  27.             }
  28.     }
  30.     #Root Domain
  31.     server {
  32.             listen 443 ssl http2; 
  33.             listen [::]:443 ssl http2;
  34.             server_name_in_redirect off;
  35.             server_name  www.mydomain.com mydomain.com;
  36.             log_not_found off;
  38.         location / {
  39.             root   /inetpub/wwwroot;
  40.             index  index.html index.htm;
  41.         }
  42.     }
  43. }

<!-- end snippet -->

答案1

得分: 2

[Final answer]

在几次测试后，以下配置几乎满足了所有先决条件。

/ 和 /files/ 都会被转发到 localhost:89/files/。

  1. server {
  2.     listen 443 ssl;
  3.     ssl_certificate .../fullchain.pem;
  4.     ssl_certificate_key .../privkey.pem;
  6.     server_name files.mydomain.com;
  8.     location /files/ { 
  9.         proxy_pass http://localhost:89/files/;
  10.     }       
  12.     location / { 
  13.         proxy_pass http://localhost:89/files/;
  14.     }
  15.     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  16.     proxy_set_header Host $host;
  17.     proxy_http_version 1.1;
  18.     proxy_set_header Upgrade $http_upgrade;
  19.     proxy_set_header Connection "upgrade";
  20. }

在这个实际情况中，只有第一次访问时会遇到一个小问题：

> 当我第一次访问 https://files.mydomain.com 时，它会自动转发到：
> https://files.mydomain.com/files/login.aspx。在我使用凭据进行身份验证后，它会自动转发到
> https://files.mydomain.com/files 而不是
> https://files.mydomain.com。但好消息是，如果我保持登录状态并重新访问 https://files.mydomain.com，
> 它将继续保持在 https://files.mydomain.com。

[Initial answer]

我知道你要求进行URL重写，但你尝试过 proxy_pass + alias 方法吗？

在我家的测试中，看起来还可以。我只是将文件放在一个文件夹中，并使用以下nginx配置（我使用8443端口作为虚假的SSL端口）：

  1. server {
  2.     listen 8443;
  3.     server_name files.ssl.localhost;
  4.     root D:/WEB;
  6.     location / {
  7.         alias D:/WEB/secretfolder/files/;
  8.         autoindex on; # 或者不用，只是用于测试文件夹列表
  9.     }
  11.     location /files/ { #注意末尾斜杠
  12.         proxy_pass http://files.ssl.localhost:8443/; #注意末尾斜杠
  13.     }
  14. }

http://files.ssl.localhost:8443/files/ 和 http://files.ssl.localhost:8443 都指向相同的目录列表：

Rewrite "https://files.mydomain.com/files" to "https://files.mydomain.com"

并且我们可以获取例如 file.txt 的内容：
Rewrite "https://files.mydomain.com/files" to "https://files.mydomain.com"

我希望这种方法符合你的目标，或者对其他人有意义。

英文:

*** [Final answer] ***

After several tests, the following configuration covers almost all the prerequisites.

Both / and /files/ are forwarded to localhost:89/files/.

  1. server {
  2. 	listen 443 ssl;
  3. 	ssl_certificate .../fullchain.pem;
  4. 	ssl_certificate_key .../privkey.pem;
  6. 	server_name files.mydomain.com;
  8. 	location /files/ { 
  9. 	    proxy_pass http://localhost:89/files/;
  10. 	}       
  12. 	location / { 
  13. 	    proxy_pass http://localhost:89/files/;
  14. 	}
  15. 	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  16. 	proxy_set_header Host $host;
  17. 	proxy_http_version 1.1;
  18. 	proxy_set_header Upgrade $http_upgrade;
  19. 	proxy_set_header Connection &quot;upgrade&quot;;
  20. }

In this real case, only a small issue at first visit :

> When I visit https://files.mydomain.com for the first time, it
> automatically forwards to:
> https://files.mydomain.com/files/login.aspx. After I authenticate with
> my credentials, it automatically forwards to
> https://files.mydomain.com/files instead of
> https://files.mydomain.com. However the good news is if I stay logged
> in and revisit https://files.mydomain.com, it will continue to stay
> at: https://files.mydomain.com.

[Initial answer]

I know you are asking for url rewriting, but have you tried the proxy_pass+alias way?

My tests at home seem ok. I simply put files in a folder and use the following nginx configuration (I use port 8443 as a fake SSL port):

  1. server {
  2. 	listen 8443;
  3. 	server_name files.ssl.localhost;
  4. 	root D:/WEB;
  6. 	location / {
  7. 	    alias D:/WEB/secretfolder/files/;
  8. 	    autoindex on; # or not, only to test folder listing
  9. 	}
  11. 	location /files/ { #beware the trailing slash
  12. 	    proxy_pass http://files.ssl.localhost:8443/; #beware the trailing slash
  13. 	}
  14. }

http://files.ssl.localhost:8443/files/ and http://files.ssl.localhost:8443 both point to the same directory listing:

Rewrite "https://files.mydomain.com/files" to "https://files.mydomain.com"

and we can get, for example, the contents of file.txt:
Rewrite "https://files.mydomain.com/files" to "https://files.mydomain.com"

I hope this approach matches your goals or makes sense for anyone else.

答案2

得分: 0

尝试使用return而不是rewrite来进行重定向。应该会起作用：

  1. location /path/to-your-page-name {
  2.   return 301 /new-path/to-your-new-page-name;
  3. }

所以，如果你想要将域名解析到~/files，并假设root指向/inetpub/wwwroot，请按照以下步骤操作：

  1. http {
  3. server {        
  4.         listen 80;
  5.         server_name  localhost;
  6.         return 301 https://$host$request_uri;
  7. }
  9. server {
  10.         listen 80;
  11.         server_name  files.mydomain.com;
  12.         location / {
  13.             return 301 https://files.mydomain.com$request_uri;
  14.         }
  15. }
  17. server {
  18.         listen 443 ssl http2; 
  19.         listen [::]:443 ssl http2;
  20.         server_name  files.mydomain.com;
  21.         client_max_body_size 0;
  22.         location / {
  23.             return 301 https://files.mydomain.com/files;
  24.         }
  25. }
  27. #根域名
  28. server {
  29.         listen 443 ssl http2; 
  30.         listen [::]:443 ssl http2;
  31.         server_name_in_redirect off;
  32.         server_name  www.mydomain.com mydomain.com;
  33.         log_not_found off;
  35.     location / {
  36.         #root   /inetpub/wwwroot;
  37.         #index  index.html index.htm;
  38.         return 301 https://files.mydomain.com/files;
  39.         }
  40.     }
  41. }

根据你的配置，你可能还需要设置server_name_in_redirect on;。希望这能帮助你！

英文:

Try using a return and not a rewrite for a redirect. This should work:

  1. location /path/to-your-page-name {
  2.   return 301 /new-path/to-your-new-page-name;
  3. }

So, if you want domains resolving to ~/files and assuming that root points to /inetpub/wwwroot do the following:

  1. http {
  3. server {        
  4.         listen 80;
  5.         server_name  localhost;
  6.         return 301 https://$host$request_uri;
  7. }
  9. server {
  10.         listen 80;
  11.         server_name  files.mydomain.com;
  12.         location / {
  13.             return 301 https://files.mydomain.com$request_uri;
  14.         }
  15. }
  17. server {
  18.         listen 443 ssl http2; 
  19.         listen [::]:443 ssl http2;
  20.         server_name  files.mydomain.com;
  21.         client_max_body_size 0;
  22.         location / {
  23.             return 301 https://files.mydomain.com/files;
  24.         }
  25. }
  27. #Root Domain
  28. server {
  29.         listen 443 ssl http2; 
  30.         listen [::]:443 ssl http2;
  31.         server_name_in_redirect off;
  32.         server_name  www.mydomain.com mydomain.com;
  33.         log_not_found off;
  35.     location / {
  36.         #root   /inetpub/wwwroot;
  37.         #index  index.html index.htm;
  38. 		   return 301 https://files.mydomain.com/files;
  39.         }
  40.     }
  41. }

You might also have to set server_name_in_redirect on; depending on your configuration.

I hope this helps!

huangapple
  • 本文由 发表于 2023年5月11日 06:12:20
  • 转载请务必保留本文链接：https://go.coder-hub.com/76222898.html
  • nginx
  • nginx-config
  • nginx-reverse-proxy
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定