Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Accessing Content Fragment using Dispatcher URL

visa679
Level 2
Level 2

We are building content fragments and exposing to Mobile App.

 

Able to get the CF json output when we use direct publish URL  https://publishURL/api/assets/abc-fragment.json

But when we use dispatcher URL(setup for our website) https://sitedomain/api/assets/abc-fragment.json we are getting page not found.

 

We do not want to use direct publish to expose Content fragments to Mobile App.

 

So do we have to configure any other settings or dispatcher rules to expose content fragment using a dispatcher vhost domain? 

 

Appreciate inputs.

 

 

Thanks.

1 Accepted Solution
asutosh_jena
Correct answer by
Community Advisor
Community Advisor

Hi @visa679 

/api needs to be allowed in the v-host and .any file for your website. Currently it will be blocked by dispatcher rule which is why you are getting a 404 response.

The same you can identify by checking the dispatcher.log as well.

 

Please apply the below entry in your filter section and it will be resolved.

/0002 { /type "allow" /url "/api/*"}

 

Links for reference:

https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/assets-api-content-fr...

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-c...

 

Thanks! 

View solution in original post

2 Replies
asutosh_jena
Correct answer by
Community Advisor
Community Advisor

Hi @visa679 

/api needs to be allowed in the v-host and .any file for your website. Currently it will be blocked by dispatcher rule which is why you are getting a 404 response.

The same you can identify by checking the dispatcher.log as well.

 

Please apply the below entry in your filter section and it will be resolved.

/0002 { /type "allow" /url "/api/*"}

 

Links for reference:

https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/assets-api-content-fr...

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-c...

 

Thanks! 

View solution in original post

visa679
Level 2
Level 2

Thanks Asutosh for the respone. We already added the filter to allow /api/assets/* path but still getting error.