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

daitienshi
daitienshi
Offline

Badges

Badges
10

Accepted Solutions

Accepted Solutions
1

Likes Received

Likes Received
2

Posts & Comments

Posts & Comments
27

Discussions

Discussions
0

Questions

Questions
0

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by daitienshi
Customize the badges you want to showcase on your profile
AEM Dispatcher not resolving vanity urls - Adobe Experience Manager 21-08-2017
Hi there,I'm trying to set up our dispatcher to resolve the vanity urls we have set up in our publisher. However, after following the configuration guide, when I try to hit a vanity url, I'm getting a 404 error rather than the page itself.Here's a snippet from our dispatcher.any configuration:Here's what I see in the dispatcher.log when I try to hit my vanity url:It looks like it's trying to get to the /home vanity url after the filter rejects it, but nothing ever shows up. When I look at the ac...

Views

4.4K

Likes

0

Replies

5
Re: Configuration of JSESSIONID cookie set by CQSE - Adobe Experience Manager 07-02-2017
Hi there,I'm in a similar situation as you with regards to configuring the cookie for all subdomains.Did you happen to find a solution to this?Thanks!

Views

867

Likes

0

Replies

0
How to configure AEM JSession cookie? - Adobe Experience Manager 07-02-2017
Hi,I've noticed that there is a cookie that AEM puts on the browser for the JSessionID.Currently, the cookie includes the fully qualified name of the AEM host, but is there a way to configure it to only look at the main domain and not the subdomain?e.g. current: aem.serverhost.com. desired: *.serverhost.comThanks in advance!

Views

493

Likes

0

Replies

0
Re: Custom repsonse header set in JSP not set via Dispatcher - Adobe Experience Manager 29-11-2016
Does this apply to both request and response headers?Feike Visser wrote... By default headers won't be cached by the dispatcher. You can configure this via the /headers section inside the cache configuration.

Views

1.1K

Likes

0

Replies

0
Re: Custom repsonse header set in JSP not set via Dispatcher - Adobe Experience Manager 29-11-2016
Thanks!However, we only need this custom response header on a particular page and it seems like overkill to have to enter all possible default headers and then this one custom one under /clientheaders. Also, my understanding is that the /clientheaders is for allowing which request headers to allow through, whereas I'm looking to get a custom response header through the dispatcher.Thoughts?Thanks again!

Views

1.1K

Likes

0

Replies

0
Custom repsonse header set in JSP not set via Dispatcher - Adobe Experience Manager 28-11-2016
I am trying to set a custom response header in my jsp via:<% response.setHeader("my-custom-header", "custom-value"); %>When I access the page directly through the Publisher, I can see the header being set. However, when I hit the same page through the Dispatcher, the header is not there.I checked the dispatcher.any file and the /clientheaders property is set to "*" to let all headers through.Would any one know why the header is not present when accessing through the Dispatcher?Thanks!

Views

2.6K

Likes

0

Replies

8
Re: Granite jQuery csrf error - Adobe Experience Manager 03-11-2016
It seems to be appearing on all pages where the granite-utils libraries are included.

Views

982

Likes

0

Replies

0
Re: Granite jQuery csrf error - Adobe Experience Manager 03-11-2016
Also, it seems because this is breaking, we are not able to use the Granite library to retrieve i18n values in javascript.

Views

982

Likes

0

Replies

0
Granite jQuery csrf error - Adobe Experience Manager 03-11-2016
Hi,Our site in AEM (6.2) uses the bundled jQuery inside Granite.From what I see, the generated granite.js file consists of the csrf.js.Currently, when a page loads, it is throwing an error in the browser console of:Uncaught TypeError: Cannot read property 'externalize' of undefined(...) getToken @ csrf.js:103The line that it's referring to in the csrf.js is:xhr.open('GET', Granite.HTTP.externalize(TOKEN_SERVLET), true);I'm not sure what is causing this (and what it's supposed to be doing even) a...

Views

1.2K

Likes

0

Replies

3
Re: AEM i18n from Javascript (try 2) - Adobe Experience Manager 03-11-2016
It seems that the generated /etc/clientlibs/granite/jquery/granite.js includes code from granite.http.externalize.js, which contains this line of code that is erroring out.I'm not sure where that granity.http.externalize.js comes from as it doesn't seem to included in the default bundle when installing AEM from scratch.Is there a way to remove that file and force the granite.js to be generated without it?Thanks!

Views

4.4K

Likes

0

Replies

2
Likes from