Is this x-robots-tag warning a false alarm or misconfig problem

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.4
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu 24.04
  • Web server and version (e.g, Apache 2.4.25):
    • Apache2 2.4.63
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Apache2 2.4.63
  • PHP version (e.g, 8.3):
    • 8.3.20
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yess
  • When did this problem seem to first start?
    • Today
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Bare Metal
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • NO

Summary of the issue you are facing:

i saw the website setting in administration overview section it report me of * Some headers are not set correctly on your instance - The X-Robots-Tag HTTP header is not set to noindex,nofollow. This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly. For more details see the documentation :arrow_upper_right:.
but in header in F12 say x-robots-tag: noindex, nofollow, noarchive, nosnippet which is even more than server documentation recommanded.
so i wonder if this is a false positive or my bad imprementation of x-robots-tag

this is curl header
HTTP/1.1 302 Found
Date: redacted
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Referrer-Policy: no-referrer-when-downgrade
Permissions-Policy: autoplay=(self), camera=(), microphone=(), geolocation=()
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Content-Security-Policy: default-src ‘self’; script-src ‘self’ ‘nonce-redacted’; style-src ‘self’ ‘unsafe-inline’; frame-src *; img-src * data: blob:; font-src ‘self’ data:; media-src *; connect-src *; object-src ‘none’; base-uri ‘self’;
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Robots-Tag: noindex, nofollow, noarchive, nosnippet
X-XSS-Protection: 1; mode=block
Referrer-Policy: no-referrer
Location: https://redacted/index.php/login
Content-Type: text/html; charset=UTF-8
Set-Cookie: oc_sessionPassphrase=redacted; path=/; secure; HttpOnly; SameSite=Lax
Set-Cookie: __Host-nc_sameSiteCookielax=true; path=/; httponly; secure; expires=Fri, 31‑Dec‑2100 23:59:59 GMT; SameSite=lax
Set-Cookie: __Host-nc_sameSiteCookiestrict=true; path=/; httponly; secure; expires=Fri, 31‑Dec‑2100 23:59:59 GMT; SameSite=strict
Set-Cookie: oc6ud7cwmbul=redacted; path=/; secure; HttpOnly; SameSite=Lax

i can provide more information if you want

That particular check is a little rigid and could probably use some refinement (i.e. see this open Issue).

P.S. When testing with curl to test/isolate the cause, make sure to use use -IL in case the problem is actually in your web server config after the redirect (doesn’t sound like it is in your case since you also looked within your browser, but noting for others that come across this).

C:\Users\user>curl -IL https://REDACTED

HTTP/1.1 302 Found
Date: REDACTED
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Referrer-Policy: no-referrer-when-downgrade
Permissions-Policy: autoplay=(self), camera=(), microphone=(), geolocation=()
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Content-Security-Policy: default-src ‘self’; script-src ‘self’ ‘nonce-REDACTED’; style-src ‘self’ ‘unsafe-inline’; frame-src *; img-src * data: blob:; font-src ‘self’ data:; media-src *; connect-src *; object-src ‘none’; base-uri ‘self’;
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Robots-Tag: noindex, nofollow, noarchive, nosnippet
X-XSS-Protection: 1; mode=block
Referrer-Policy: no-referrer
Location: https://REDACTED/index.php/login
Content-Type: text/html; charset=UTF-8
Set-Cookie: oc_sessionPassphrase=REDACTED; path=/; secure; HttpOnly; SameSite=Lax
Set-Cookie: __Host-nc_sameSiteCookielax=true; path=/; httponly; secure; expires=REDACTED; SameSite=lax
Set-Cookie: __Host-nc_sameSiteCookiestrict=true; path=/; httponly; secure; expires=REDACTED; SameSite=strict
Set-Cookie: oc6ud7cwmbul=REDACTED; path=/; secure; HttpOnly; SameSite=Lax

HTTP/1.1 200 OK
Date: REDACTED
Server: Apache
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Referrer-Policy: no-referrer-when-downgrade
Permissions-Policy: autoplay=(self), camera=(), microphone=(), geolocation=()
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
X-Request-Id: REDACTED
Cache-Control: no-cache, no-store, must-revalidate
Content-Security-Policy: default-src ‘none’; base-uri ‘none’; manifest-src ‘self’; script-src ‘nonce-REDACTED’ blob:; script-src-elem ‘strict-dynamic’ ‘nonce-REDACTED’ blob:; style-src ‘self’ ‘unsafe-inline’; img-src ‘self’ data: blob: https://*.tile.openstreetmap.org; font-src ‘self’ data:; connect-src ‘self’ blob: stun.nextcloud.com:443; media-src ‘self’ blob:; frame-src ‘self’; child-src blob: ‘self’; frame-ancestors ‘self’; worker-src blob: ‘self’; form-action ‘self’
Feature-Policy: autoplay ‘self’; camera ‘self’; fullscreen ‘self’; geolocation ‘none’; microphone ‘self’; payment ‘none’
X-Robots-Tag: noindex, nofollow, noarchive, nosnippet
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-XSS-Protection: 1; mode=block
Referrer-Policy: same-origin
Content-Length: 24555
Content-Type: text/html; charset=UTF-8
Set-Cookie: oc_sessionPassphrase=REDACTED; path=/; secure; HttpOnly; SameSite=Lax
Set-Cookie: __Host-nc_sameSiteCookielax=true; path=/; httponly; secure; expires=REDACTED; SameSite=lax
Set-Cookie: __Host-nc_sameSiteCookiestrict=true; path=/; httponly; secure; expires=REDACTED; SameSite=strict
Set-Cookie: oc6ud7cwmbul=REDACTED; path=/; secure; HttpOnly; SameSite=Lax

i just read the Issue on github. So is it safe to ignore it if it impremented correctly.

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.