Skip to content

Updates for Nextcloud security checks #442

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hollanbm wants to merge 3 commits into from
Closed

Updates for Nextcloud security checks #442

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ebc2d55
Updates for NextCloud security checks
hollanbm May 10, 2022
d99cbfd
refactor location blocks
hollanbm May 10, 2022
759ee5a
update sample date
hollanbm May 10, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion nextcloud.subdomain.conf.sample
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
## Version 2021/05/18
## Version 2022/05/10
# make sure that your dns has a cname set for nextcloud
# assuming this container is called "swag", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
Expand Down Expand Up @@ -33,4 +33,14 @@ server {

proxy_max_temp_file_size 2048m;
}

# The rules in this block are an adaptation of the rules
# in the Nextcloud `.htaccess` that concern `/.well-known`.
location ^/.well-known/(caldav|carddav) {
return 301 $scheme://$host/remote.php/dav;
}

# Let Nextcloud's API for `/.well-known` URIs handle these
# requests by passing them to the front-end controller.
rewrite ^/.well-known/(webfinger|nodeinfo) /index.php$uri redirect;
}