I have written Dispatcher rewrite to shorten the URL. Urls are being shortened but the page is not rendering anything it is appearing blank.
Model JSON is loading fine on both Publish and Dispatcher content is exactly the same. Screenshot is attached below
On Publish env
On Dispatcher
What shall I do now? I am confused
Views
Replies
Total Likes
it seems you clientlibs are not loading, can you check is proxy enabled for the required clientlibs or not?
Clientlibs are loading that icon is coming because of HTTP request. I tried to open in new tab it has the data
Can you check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-spa-react-dispatcher-s... for dispatcher setup with AEM SPA project.
Also, check AEM and dispatcher logs to see any error.
Hi @rawvarun
Yes, I check that solution out. My model json and the path are the same as well as there are no errors on the Dispatcher log.
For frontend changes, I followed https://experiencing150.rssing.com/chan-25971229/article453.html
I don’t see .html file extension fir the dispatcher url. Can you check with .html extension for dispatcher url as well or you have setup on dispatcher to work as extension less url?
So when you request page from dispatcher does the request going to aem publisher and if not then you might need to check the dispatcher rules for shortened url
How can I verify that?
My Dispatcher code
Check request.log and access.log of aem publisher
Request and access log are empty of publish, whenever I request 4503 then only it is printing someting. On hitting dispatcher url no log is printed on request.log and access.log
That means your dispatcher is not configured correctly. You need to debug on the dispatcher by setting the dispatcher log as debug and check what happens with the request
Is the request going as full path to publisher from dispatcher after you rewrite in dispatcher?. It seems publisher could not process shorten url. We can enable shorten url using JcrResourceResolverFactoryImpl. Please check the below article.
https://blogs.perficient.com/2021/01/11/unit-testing-jcr-resource-resolver-mappings/
How can I verify that request is going to publish. Currently, I just have a dispatcher which is handling everything.
we are also facing similar issue. Was there any solution for this?
Views
Replies
Total Likes