mirror of
https://github.com/nextcloud/documentation.git
synced 2025-10-26 11:18:02 +00:00
add server_port variable to well-known redirects
if Nextcloud is used on a custom HTTPS port, the well-known redirects do not work, because the server port is not included in the redirect.
This commit is contained in:
parent
dfaa88f693
commit
6cc257a017
@ -42,7 +42,7 @@ webroot of your nginx installation. In this example it is
|
||||
listen [::]:80;
|
||||
server_name cloud.example.com;
|
||||
# enforce https
|
||||
return 301 https://$server_name$request_uri;
|
||||
return 301 https://$server_name:443$request_uri;
|
||||
}
|
||||
|
||||
server {
|
||||
@ -95,10 +95,10 @@ webroot of your nginx installation. In this example it is
|
||||
# rewrite ^/.well-known/webfinger /public.php?service=webfinger last;
|
||||
|
||||
location = /.well-known/carddav {
|
||||
return 301 $scheme://$host/remote.php/dav;
|
||||
return 301 $scheme://$host:$server_port/remote.php/dav;
|
||||
}
|
||||
location = /.well-known/caldav {
|
||||
return 301 $scheme://$host/remote.php/dav;
|
||||
return 301 $scheme://$host:$server_port/remote.php/dav;
|
||||
}
|
||||
|
||||
# set max upload size
|
||||
@ -199,7 +199,7 @@ your nginx installation.
|
||||
listen [::]:80;
|
||||
server_name cloud.example.com;
|
||||
# enforce https
|
||||
return 301 https://$server_name$request_uri;
|
||||
return 301 https://$server_name:443$request_uri;
|
||||
}
|
||||
|
||||
server {
|
||||
@ -248,10 +248,10 @@ your nginx installation.
|
||||
# rewrite ^/.well-known/webfinger /nextcloud/public.php?service=webfinger last;
|
||||
|
||||
location = /.well-known/carddav {
|
||||
return 301 $scheme://$host/nextcloud/remote.php/dav;
|
||||
return 301 $scheme://$host:$server_port/nextcloud/remote.php/dav;
|
||||
}
|
||||
location = /.well-known/caldav {
|
||||
return 301 $scheme://$host/nextcloud/remote.php/dav;
|
||||
return 301 $scheme://$host:$server_port/nextcloud/remote.php/dav;
|
||||
}
|
||||
|
||||
location /.well-known/acme-challenge { }
|
||||
|
||||
Loading…
Reference in New Issue
Block a user