8/28/2023 0 Comments Noindex nofollowI found another site where someone advised that he had it configured inside nextcloud docker and npm docker also. Integrity check in nextcloud cli returns no issues. # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years) In NPM docker, Nginx-Proxy-Manager-Official/data/nginx/proxy_host/1.conf has: # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)Īdd_header Strict-Transport-Security "max-age=63072000 includeSubDomains preload" always Īdd_header X-Robots-Tag "noindex, nofollow" always Īccess_log /data/logs/proxy-host-1_access.log proxy Įrror_log /data/logs/proxy-host-1_error.log warn Within nextcloud docker, /nextcloud/nginx/site-confs/nf has # HTTP response headers borrowed from Nextcloud `.htaccess`Īdd_header Referrer-Policy "no-referrer" always Īdd_header X-Content-Type-Options "nosniff" always Īdd_header X-Download-Options "noopen" always Īdd_header X-Frame-Options "SAMEORIGIN" always Īdd_header X-Permitted-Cross-Domain-Policies "none" always Īdd_header X-Robots-Tag "noindex, nofollow"Īdd_header X-XSS-Protection "1 mode=block" always I have tried everything I found so far, without luck. I am using docker installation, and separate docker for Nginx-proxy-manager. This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. I have tried everything so far, but nextcloud just keeps complaining: The "X-Robots-Tag" HTTP header is not set to "noindex, nofollow". What is the nextcloud.inc line supposed to be? I have read all the links on this page but i am still in the dark? I have cleared the browser cache many times. I tried occ # occ -vv integrity:check-core No errors found The "X-Robots-Tag" HTTP header is not set to "noindex, nofollow". usr/local/etc/rc.d/nginx: WARNING: failed to start nginxĪdd_header X-Robots-Tag “noindex,nofollow” always Nginx: configuration file /usr/local/etc/nginx/nf test failed Nginx: invalid number of arguments in "add_header" directive in /usr/local/etc/nginx/conf.d/nextcloud.inc:23 Performing sanity check on nginx configuration: I would say, that your “Workaround” is more than that, it looks like the solution.Īdd_header X-Robots-Tag “noindex, nofollow” always I know how to do it for apache2 but have no clue how to translate this to nginx. htaccess parsing (with AllowOverride None) for performance reasons or nginx users must change their webserver conf files accordingly. New: ErrorDocument 403 /index.php/error/403įor people who disabled. New: # Add cache control for static resources Header set Cache-Control "max-age=15778463, immutable" Header set Cache-Control "max-age=15778463" Old: # Add cache control for static resources New: Header always set X-Robots-Tag "noindex, nofollow" Old: Header always set X-Robots-Tag "none" Because “none” is indeed equivalent to “noindex, nofollow” for Google, but seems to be not supported by Bing and probably other search engines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |