5 replies

'content-type' header issue when validating ApplePay Well Known Association file in Pages instance

Hi there, I've been directed here from CloudFlare Support.

I have an Apple Well Known verification file saved in my Pages application:

https://checkouttemp-dev.shopthru.dev/.well-known/apple-developer-merchantid-domain-association

For the Pages project

shopthru-checkout-dev.pages.dev

shopthru-checkout-dev.pages.dev

which has the latest Production deployment of https://454ea75a.shopthru-checkout-dev.pages.dev.

Account ID: c18d716869a1d1fb1b4d36b576f6929c

The file can be loaded via a browser and a

curl -I https://checkouttemp-dev.shopthru.dev/.well-known/apple-developer-merchantid-domain-association

curl -I https://checkouttemp-dev.shopthru.dev/.well-known/apple-developer-merchantid-domain-association

responds as expected (well, I think).

However when I use this tool to validate the file (enter checkouttemp-dev.shopthru.dev as the Domain):

https://branch.io/resources/aasa-validator/

It shows a validation error of:

"Your file's 'content-type' header was not found or was not recognized."

I have been trying things like setting the correct headers in a _headers file for this project:

/.well-known/apple-developer-merchantid-domain-association
Content-Type: text/plain; charset=utf-8
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
ETag: ""
Accept-Ranges: bytes

/.well-known/apple-developer-merchantid-domain-association
Content-Type: text/plain; charset=utf-8
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
ETag: ""
Accept-Ranges: bytes

But to no avail. I believe there's something intrinsic about Pages going on here?

- This issue is present whether or not I use the default domain (shopthru-checkout-dev.pages.dev) or the custom domain (checkouttemp-dev.shopthru.dev).

- This validation error is occurring with known good files Association files as well.

- This validation passes when run against the same field served from Google Cloud in a side experiment.

Are there any known issues with Pages and Apple Well Known files around headers etc?

Thanks

'content-type' header issue when validating ApplePay Well Known Association file in Pages instance

shopthru-checkout-dev.pages.dev

shopthru-checkout-dev.pages.dev

which has the latest Production deployment of https://454ea75a.shopthru-checkout-dev.pages.dev.

Account ID: c18d716869a1d1fb1b4d36b576f6929c

The file can be loaded via a browser and a

curl -I https://checkouttemp-dev.shopthru.dev/.well-known/apple-developer-merchantid-domain-association

curl -I https://checkouttemp-dev.shopthru.dev/.well-known/apple-developer-merchantid-domain-association

/.well-known/apple-developer-merchantid-domain-association
Content-Type: text/plain; charset=utf-8
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
ETag: ""
Accept-Ranges: bytes

/.well-known/apple-developer-merchantid-domain-association
Content-Type: text/plain; charset=utf-8
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
ETag: ""
Accept-Ranges: bytes

'content-type' header issue when validating ApplePay Well Known Association file in Pages instance

Similar Threads

'content-type' header issue when validating ApplePay Well Known Association file in Pages instance

Similar Threads

Similar Threads

Similar Threads