Getting 404 while loading experience fragment in DNS userinfo.json and undefined | Community
Skip to main content
keshava219
Level 3
May 13, 2022
Solved

Getting 404 while loading experience fragment in DNS userinfo.json and undefined

  • May 13, 2022
  • 2 replies
  • 1833 views

Getting 404 while loading experience fragment in DNS userinfo.json and undefined

 

but working in author mode please let me know how to handle this 404 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ArpitVarshney

Hi @keshava219 
It is giving a 404 error which means not found.

Click on this request and try to see the path which it is trying to access and check:

  • check whether it is accessible in publisher or not, if not that means your experience fragment is not published. Please publish and check again.
  • If it's already published and can be accessed at the publisher then your dispatcher is blocking it. Check dispatcher logs and allow it.

Regards,

Arpit V

2 replies

MayurSatav
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 13, 2022

Hi @keshava219 ,

 

Could you please share what is the exact use case?. If you want to expose your experience fragment in JSON then you can simply publish your experience fragment and remove editor.html from the URL then add fragmentname.model.json.

 

e.g.

Consider this is your EF.

http://localhost:4502/editor.html/content/experience-fragments/my-site/recipes/master.html

 

then URL should be like this

 

http://localhost:4502/content/experience-fragments/my-site/recipes/master.model.json

 

 

 

keshava219
Level 3
May 13, 2022

hi @mayursatav ,

 

            this experience fragment included on any a page and in that page we are calling experience fragment as a button option, So while loading EF we are facing time loading issue of "userinfo.json" taking 10 sec max time  of loading.

 

 

MayurSatav
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 13, 2022

Could you please share the error log?

ArpitVarshney
Community Advisor
ArpitVarshneyCommunity AdvisorAccepted solution
Community Advisor
May 13, 2022

Hi @keshava219 
It is giving a 404 error which means not found.

Click on this request and try to see the path which it is trying to access and check:

  • check whether it is accessible in publisher or not, if not that means your experience fragment is not published. Please publish and check again.
  • If it's already published and can be accessed at the publisher then your dispatcher is blocking it. Check dispatcher logs and allow it.

Regards,

Arpit V

keshava219
Level 3
May 18, 2022

Hi @arpitvarshney ,

 

             Thanks a lot working fine now. but undefined still showing on both author and dispatcher