Currently, on deployment tiers like sandbox and production, the content source response body is suppressed for non-200 response codes to prevent error stacks that might contain sensitive information from being returned.
However this is blocking our ability to replace the Mobile APP middleware which relies on HTTP 415 responses with JSON response body with an Outbound Feeds solution.
Could there be a way to configure a content source to support a response body for certain codes?
John Flaherty
Hi John,
Thanks for submitting this idea. The use case you describe definitely makes sense. Although, it requires multiple teams to collaborate on the solution and it is a sensitive change that we want to make sure it's backward compatible.
We are marking it as "future consideration" and will plan in the future Engine release.