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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

tatvam
tatvam
Offline

Badges

Badges
10

Accepted Solutions

Accepted Solutions
1

Likes Received

Likes Received
13

Posts

Posts
15

Discussions

Discussions
3

Questions

Questions
12

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by tatvam
Customize the badges you want to showcase on your profile
Re: Forbidden - 403 - Adobe Experience Manager 14-09-2020
Since you are getting 403 due to default GET servlet, this means that the URL is not mapping to a resource. It is possible the "provided navigation option" was generated wrong. It is possible the trailing / is to blame and could be checked first. Additionally see if the servlet (as a component) and the bundle are active.

Views

544

Likes

2

Replies

0
Re: AEM Dispatcher considers sitemap as vanity URL - Adobe Experience Manager 14-09-2020
Found the answer, but it took a while dealing with environments with restrictive permissions.1) The dispatcher filter rules were correct. 2) No need to remove the vanity URLs section3) Found that the DNS routed the traffic to a different vhost in this multi-vhost environment4) And this routed the traffic subsequently to wrong dispatcher farm. In short, dispatcher behaved correctly as expected - meaning it got a 404 in filters and thus routed to vanity URLs - just that it happened in the wrong di...

Views

822

Likes

0

Replies

0
Re: AEM Dispatcher considers sitemap as vanity URL - Adobe Experience Manager 10-09-2020
@sashi_mulugu does dispatcher treat xml extensions as vanity URLs? All other URLs are not treated like this and are getting rendered fine.

Views

870

Likes

0

Replies

0
AEM Dispatcher considers sitemap as vanity URL - Adobe Experience Manager 10-09-2020
We have sitemap configured as /en/sitemap.xmlThis is working as expected in the publisher. However while accessing from dispatcher, see the following the dispatcher logUnable to fetch vanity URLs from [ip-address]:4503/libs/granite/dispatcher/content/vanityUrls.html: remote server returned: HTTP/1.1 404 Not Found [Thu Sep 10 21:37:51 2020] [I] [pid 79557] "GET /[path-to-en]/en/sitemap.xml" ! - 9ms [publishfarm/-]It seems like the sitemap is treated as vanity URL. Any thoughts on how to prevent t...

Views

900

Likes

0

Replies

5
Re: Child pages being overwritten in English after root p... - Adobe Experience Manager 01-07-2020
You might want to uncheck isDeep property. This is explained here - https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/tc-rules.html

Views

633

Like

1

Replies

1
Re: Find out all the Heavy query components in AEM6.3 - Adobe Experience Manager 30-06-2020
You would want to verify what @Jaideep_Brar suggests. Assuming you are talking about page load time in your "site", there might be other factors at play as well Cache ratioSpecific component logicVolume of trafficClientlibs load time in browserbreaking JSIf in author, also look at the "developer mode". It should give you component wise breakdown on loading time.

Views

571

Like

1

Replies

0
Re: Change password is not working - Adobe Experience Manager 30-06-2020
When you say homepage, this is AEM Admin page? Or is the homepage part of the site you built on AEM? In any case, for such errors, you need to troubleshoot, starting with the logs.

Views

2.5K

Like

1

Replies

1
Re: can we enable style system in classic template? - Adobe Experience Manager 29-06-2020
If I have to think through the need for this, I can assume that 1) You have (to manage) static and editable templates2) (at least some of the )New components need to be supported in both static and editable templates3) Since one is developing components with style system, might want to leverage the style system concept in static as well. Otherwise, one might as well migrate the static to editable templates. Seems like for some reason you don't want to do that. Anyways, leaving the issues related...

Views

459

Like

1

Replies

0
Re: AEM 6.5 asset rendering issue - Adobe Experience Manager 29-06-2020
It is possible Chrome would be expecting some headers that is missing in 6.5 vs 6.4. You might want to scan the response headers in 6.4 vs 6.5 and find if something might be missing.

Views

501

Like

1

Replies

0
Re: Change page name - Adobe Experience Manager 29-06-2020
Try "Move" Page option

Views

2.7K

Like

1

Replies

0