How to properly configure apple-app-site-association file in pagoda nginx to avoid 404 errors?

Detailed explanation of Apple-App-Site-Association file configuration on Baota Nginx server and 404 error solution

Recently, the iOS team provided an apple-app-site-association file that needs to be correctly configured to the Nginx server managed by the Pagoda Panel. However, after multiple attempts, there is still an error of 404. This article will analyze in detail what may cause this problem in Nginx configuration and provide effective solutions.

The root cause of the problem lies in Nginx's location block matching rules. Since there are multiple location blocks in the configuration file and the regular expression matching priority is higher than the exact match, the server preferentially matches to other location blocks rather than location block where the target file is located. To verify this, you can add the access_log directive in location block that is suspected to be matched first, and record the access log for troubleshooting.

To avoid 404 errors, we need to modify the Nginx configuration to ensure that apple-app-site-association file is matched exactly. The following exact matching rules are recommended:

location = /.well-known/apple-app-site-association {
    #Configuration item default_type application/json;
    # Replace with your actual content return 200 '{"applinks":{"apps":[],"details":[{"appID":"Your AppId","paths":["*"]}]}}';
}

By using the exact matching method of location = ... , Nginx will directly match the / path, thus correctly returning the file contents, solving the 404 error. Be sure to replace "你的AppId" with your actual App ID. Also, make sure the file permissions are correct and allow the server to read the file.

The above is the detailed content of How to properly configure apple-app-site-association file in pagoda nginx to avoid 404 errors?. For more information, please follow other related articles on the PHP Chinese website!