1

Here is my nginx configuration

server {
   root /home/ubuntu/www
   ...
   location = /apple-app-site-association {
        default_type 'application/json';
   }
   location = /.well-known/apple-app-site-association {
        default_type 'application/json';
   }
    ...
}

and the curl output is

› curl -I https://example.com/.well-known/apple-app-site-association
HTTP/2 200
content-type: application/json
vary: Accept-Encoding
strict-transport-security: max-age=31536000
accept-ranges: bytes

However apple is giving me this, any idea?

Apple-app-site-association

niksmac
  • 2,667
  • 3
  • 34
  • 50
  • Have you tried to request the web server with an external server (or service like https://reqbin.com/curl ) sending the request rather using your own computer? I've been tricked before by my own computer for problems like this ;) – imgg Nov 13 '20 at 16:58
  • What is the corresponding line from the nginx error log? – Ivan Shatsky Nov 13 '20 at 18:29
  • @imgg curl give me expected result, content type and json output – niksmac Nov 14 '20 at 15:04
  • @IvanShatsky why do you think there is an error? As per the implementation the page should deliver with content type json and json output in browser which is happening accurately. Am I missing something? – niksmac Nov 14 '20 at 15:05
  • @niksmac I don't know what is the reason of this issue, but every 50x error had an according entry in the nginx error log. Checking it may give some clue on how to fix this. – Ivan Shatsky Nov 14 '20 at 15:08
  • @IvanShatsky calls form Search API Validation Tool are not even reaching my server, nothing in access or error log. – niksmac Nov 15 '20 at 02:16
  • @IvanShatsky I am getting this error it turns out to be apple bot `connect() failed (111: Connection refused) while connecting to upstream, client: 17.58.99.163, server: 0.0.0.0:443, upstream: "127.0.0.1:5349", bytes from/to client:0/0, bytes from/to upstream:0/0` – niksmac Nov 15 '20 at 02:39
  • All I can tell is that you need to find out how that request differ from the `curl` one. This error log line should be followed with the request line, check it and try to reproduce exactly that request with the `curl`. Check the TLS ciphers you are using via the `https://www.ssllabs.com/ssltest/` - are there any anomalies with the Apple systems? – Ivan Shatsky Nov 15 '20 at 05:20

0 Answers0