Hi ,
I have used context hub in my template as below:
<sly data-sly-resource="${'contexthub' @ resourceType='granite/contexthub/components/contexthub'}"/>
However on publish instance I get a 404 for below url
http://localhost:4503/etc/cloudsettings/default/contexthub.kernel.js ---> Giving 404
I also get a 404 error in chrome browswer console for this js file.
However in Author this works fine.
http://localhost:4502/etc/cloudsettings/default/contexthub.kernel.js ---> Loading fine
Any help is really appreciated.
Thanks
Hina
Views
Replies
Total Likes
Enabled the below urls in the Dispatcher's publish-farm.any
/0010 { /type "allow" /url "/etc/cloudsettings*" }
/0011 { /type "allow" /url "/etc/segmentation*" }
Something similar reported here:- Re: ContextHub experiences not showing on AEM 6.2 Publish instance
Views
Replies
Total Likes
Thank you for the response. I added the below entries in dispatcher publish farm file.
/0080 { /type "allow" /method "GET" /url "/libs/cq/personalization/*" }
/0081 { /type "allow" /method "GET" /url "/etc/segmentation.segment.js" }
/0082{ /type "allow" /url "/etc/cloudsettings*" }
/0083 { /type "allow" /url "/etc/segmentation*" }
Now i see more errors in browswer console
Below json file gives 404
http://xxxdomain.com/abc/jcr:content/contexthub.pagedata.json --> 404
/jcr:content/contexthub.commerce.cart.json --> 404
/jcr:content/contexthub.commerce.orderhistory.json --> 404
/jcr:content/contexthub.commerce.relatedproducts.json --> 404
Does Adobe have any documentation as to what needs to be opened in the Dispatcher when using the “granite/contexthub/components/contexthub” resource?
Just to let you know i am using AEM 6.2
Thanks
Hina
Hi Hina,
Wanted to know if you found a resolution to the 404 errors mentioned in your post here.
I am facing the same error and i am working on AEM 6.4.
Regards,
Bhaskar
Check does the anonymous user has read permission to the /etc/segmentation in publish.
Hi, did you get any solution to this? We are also getting these json related errors in the console in 6.5.
Hi, has anybody found a workaround for this? (I am using 6.5.4)
Same error, it works in author, and in publish I get a 404 (hitting the instance directly).
This other post proposes a workaround to make the contexthub.kernel.js show up in publish instances.
It worked for me, probably it can help somebody else as well.
Views
Likes
Replies