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

Bruce_Lefebvre
Bruce_Lefebvre
Offline

Badges

Badges
17

Accepted Solutions

Accepted Solutions
28

Likes Received

Likes Received
30

Posts

Posts
63

Discussions

Discussions
6

Questions

Questions
57

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by Bruce_Lefebvre
Customize the badges you want to showcase on your profile
Re: Using Content Transfer Tool - From AEM instance to a Cloud Service instance | AEM Community Blog Seeding - Adobe Experience Manager 04-08-2021
Hello @asn_india, > Would you be able to share some statistics around the usage of content transfer tool? interested in assets migration from non-cloud to cloud(6.4 to cloud)Adobe has introduced a new tool called the Cloud Acceleration Manager which will be able to help answer these questions, in addition to helping with other aspects of the transition journey starting from planning to going live on Cloud Service. > What is a comfortable set size?This depends on the configuration of AEM's data s...

Views

207

Like

1

Replies

0
Re: Hi Team, When running the dispatcher tool , we got belo... - Adobe Experience Manager 06-05-2021
Hi @niks1, Looks to me like the issue is the inclusion of the text "*.1.json" in this line. If you would like to enable the use of the "1" selector, you could add a `/selectors` element to the rule. Details can be found here (look for "/selectors" on the page for examples): https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#restricting-query-strings

Views

612

Like

1

Replies

0
Re: Introducing the AEM Dispatcher Optimizer Tool | AEM Community Blog Seeding - Adobe Experience Manager 07-04-2021
Hi, Have you tried running the DOT Maven Plugin on your codebase locally? Details can be found here: https://github.com/adobe/aem-dispatcher-optimizer-tool/tree/main/plugin#use-from-an-aem-archetype-based-project There are additional details logged which may help us understand what's going on. For example, if there are 2 dispatcher.any files in the configuration, the DOT may be analyzing the wrong one, which could lead to it not picking up the changes you've made to the active configuration. If ...

Views

741

Likes

2

Replies

0
Re: What do people think about the dispather recommendati... - Adobe Experience Manager 22-03-2021
@BrettBirschbach wrote:That said, what are your thoughts on why the dispatcher forwards query parameters ignored for caching purposes to the AEM server?Good question. I've raised this internally and will share an update when I know more. Thanks again for sharing your concerns about this rule. It's led to a good discussion on our team, and we've updated the ignoreUrlParams rule description with a "Security Caveat" section.

Views

719

Like

1

Replies

0
Re: What do people think about the dispather recommendati... - Adobe Experience Manager 17-03-2021
This doesn't change my major concern...that the system is NON-secure by default [..] In the past, the default dispatcher configuration was that any query parameter circumvents the dispatcher cache. Just to clarify: the default configuration — included when a project is bootstrapped with the AEM archetype — has not changed (ignoreUrlParams remains commented out). We acknowledge that the creation and maintenance of the allow list rules (ignoreUrlParams, Sling selectors, and Sling suffixes) is goin...

Views

717

Like

1

Replies

0
Re: What do people think about the dispather recommendati... - Adobe Experience Manager 15-03-2021
Hi Brett, Thanks for sharing these concerns - appreciate your perspective on this. We anticipated questions about this rule and created the first video in our DOT "rule explainer" series to go over our motivation for the ignoreUrlParams rule: https://youtu.be/jgs_0EitZGg Sure, it increases the default cache hit ratio, but that was something we already accomplish in the past by configuring query parameters to be ignored In our experience we've found that unexpected/unforeseen query params often e...

Views

787

Like

1

Replies

0
Re: Experience Fragment issue in Dispatcher - Adobe Experience Manager 30-09-2020
Hello, The exact behaviour of the dispatcher in this situation will depend on your configuration:Is the dispatcher configured to use TTLs (via the `/enableTTL` setting)?Or, is it using .stat file based invalidation with a dispatcher flush agent?In case #1 above, the time-to-live on the content in question (often set with the ACS AEM Commons Dispatcher TTL feature) will need to expire before the page will be "refetched" from the publish tier. In case #2, .stat files will be "touched" in the cache...

Views

1.7K

Likes

2

Replies

0
Re: How does the dispatcher flush do invalidation rather... - Adobe Experience Manager 15-09-2020
Yes, this feature still uses the standard flush agent URI (http://host:port/dispatcher/invalidate.cache), but changes the HTTP method to POST and uses the custom serialization type which is implemented in this example code (and intended to be customized for your own use case): https://github.com/cqsupport/webinar-dispatchercache/blob/master/src/refetching-flush-agent/refetch-bundle/src/main/java/com/day/cq/replication/dispatcher/DispatcherFlushContentBuilder.java

Views

544

Likes

0

Replies

0
Re: How does the dispatcher flush do invalidation rather... - Adobe Experience Manager 15-09-2020
Hi @James_Appleby, Are you familiar with the concept of a Re-fetching Flush? The "Optimizing the Dispatcher cache" doc has details on this approach: https://helpx.adobe.com/ca/experience-manager/kb/optimizing-the-dispatcher-cache.html#refetching-flush We've written a few lab-format dispatcher experiments to raise awareness about some of the dispatcher's features, and the first one is on the "Effect of Re-fetching Dispatcher Flush": https://github.com/adobe/aem-dispatcher-experiments#experiments ...

Views

571

Likes

2

Replies

2
Re: "mailto:" and "tel:" links do not work in InAppBrowser (Android only) - Adobe Experience Manager Mobile 15-09-2017
OK, after a bit of digging I've got a workaround that supports both iOS and Android. This is the body of my .article HTML page: Open page with a mailto: function openLinkInBrowser(url) { if (navigator && navigator.app && navigator.app.loadUrl) { navigator.app.loadUrl(url, { openExternal:true }); } else { window.open(url, '_system'); } } ... the navigator.app.loadUrl(..) call was the key missing piece. Answer was found on this SO thread: html5 - phonegap open link in browser - Stack Overflow Let me know if this works for you.

Views

6.2K

Like

1

Replies

0