Not able to access AEM experience fragments directly in publisher

[Vishnu9]

we are using AEM as a cloud service.

Able to access experience fragment and its JSON data  in author 

https://author-p***-e***.adobeaemcloud.com/content/experience-fragments/Brand/us/en/site/header/mast...

https://author-p***-e***.adobeaemcloud.com/content/experience-fragments/Brand/us/en/site/header/mast...

but unable to access the same in publisher 

https://publish-p***-e***.adobeaemcloud.com/content/experience-fragments/Brand/us/en/site/header/mas...

https://publish-p***-e***.adobeaemcloud.com/content/experience-fragments/Brand/us/en/site/header/mas...

Do we need to enable some settings in dispatcher ?

How to expose  experience fragments data to 3rd party (not AEM target) either in html or json .

Do we need to write any custom logic to  expose XF  in publisher ?

[arunpatidar]

Hi @Vishnu9 

Please review the dispatcher filter rules to allow direct access to XF from Publishers.

Custom Solution : To make XF accessible to a third party, you can implement a solution similar to the "Export to Target" feature in AEM Author. Alternatively, you can create a service on the publisher that exposes all the XFs intended for third-party access. The third party can then retrieve these as a listing and access additional XF data. The content can be exposed in either HTML or JSON format.

[narendiran_ravi · Accepted solution]

OOB we have the selector -.plain to display XF as plain HTML. Refer -https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/ext... 

[RajaShankar]

Hi @Vishnu9 

I am able to access Experience Fragment in my author as well as publisher cloud environment. By default it works. Could you please try from your publisher using CDN domain instead of direct URL Example

https://aem-qa.xyz.com/content/experience-fragments/weretail/ca/en/master.model.pretty.json

Regards,

Rajashankar.R