How to debug Sling JSON Exporter issues?

Hi @donquixote_dofl,

1. Check Request Accept Header

• The .infinity.json suffix should return JSON regardless, but if there’s a difference in the Accept HTTP header (e.g., one environment treats it differently), it could affect Sling’s response type negotiation.

• Use a tool like Postman or curl to compare request headers exactly between environments.

curl -I https://yourserver/content/sites/na/us/en/samplepage.infinity.json

2. Verify Sling Resource Resolution and Selectors

• Confirm the .infinity.json selector is correctly recognized.

• Make sure both environments have the same Sling Resource Types and Servlet Mappings.

• If the resource type or script rendering JSON is missing or overridden in one environment, it might fallback to HTML.

Did you check error logs? in both environments?

Review the AEM error logs (error.log) in both environments for any exceptions or warnings when accessing .infinity.json.
Look for issues related to Sling Models, resource resolution, or servlet handling.

Check Sling Mappings and Resource Resolution
Verify if there are any differences in the Sling Resource Resolver configurations between the two environments.
Go to /system/console/configMgr and check the Apache Sling Resource Resolver Factory configuration.
Ensure that the JSON extension is not being overridden or mapped differently in one environment.