Configuration Warnings

[asmitconsulting]

The following warnings will be displayed on my NAS after successful installation:

• Your web server is not configured correctly to resolve "/.well-known/caldav". For more information, see the documentation.
• Your web server is not configured correctly to resolve "/.well-known/carddav". For more information, see the documentation.
• The "Referrer-Policy" HTTP header is not set to "no-referrer", "no-referrer-when-downgrade", "strict-origin" or "strict-origin-when-cross-origin". This allows reference information to be disclosed. See the W3C recommendation. How can these be fixed or could you correct the configuration in the same way? Thank you

[yeoldegrove]

The "Referrer-Policy" HTTP header is not set to "no-referrer", "no-referrer-when-downgrade", "strict-origin" or "strict-origin-when-cross-origin". This can leak referer information. See the W3C Recommendation. This is fixed by the commit in #38.

[PhiGi87]

Unfortunately there will be more warnings with every update. Are you so nice to fix the problem? I would be very grateful to you.

[kw90]

The first two warnings seem also to cause the proposed URI for synchronizing with iOS to fail (See issue over at NextCloud documentation GitHub).

Looking at the General troubleshooting documentation and the example Nginx configuration this could be solved by properly setting the .well-known URI for service discovery. Adding the following lines to the Nginx configuration could do the trick

    location = /.well-known/carddav {
      return 301 $scheme://$host:$server_port/remote.php/dav;
    }
    location = /.well-known/caldav {
      return 301 $scheme://$host:$server_port/remote.php/dav;
    }

[tutu20120501]

The first two warnings seem also to cause the proposed URI for synchronizing with iOS to fail (See issue over at NextCloud documentation GitHub).

Looking at the General troubleshooting documentation and the example Nginx configuration this could be solved by properly setting the .well-known URI for service discovery. Adding the following lines to the Nginx configuration could do the trick

    location = /.well-known/carddav {
      return 301 $scheme://$host:$server_port/remote.php/dav;
    }
    location = /.well-known/caldav {
      return 301 $scheme://$host:$server_port/remote.php/dav;
    }

U R RIGHT. The warnnings is from here. U must correct it as below: location = /.well-known/carddav { return 301 $scheme://$http_host/remote.php/dav; } location = /.well-known/caldav { return 301 $scheme://$http_host/remote.php/dav; }