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

15473203
15473203
Offline

Badges

Badges
8

Accepted Solutions

Accepted Solutions
1

Likes

Likes
2

Posts

Posts
10

Discussions

Discussions
0

Questions

Questions
10

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by 15473203
Customize the badges you want to showcase on your profile
Re: SimpleSearch with Unicode Characters Takes Long Time/Crashes Instance
Avatar
Ignite 100
Level 10
smacdonald2008
Level 10

Likes

1,430 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Ignite 100
Ignite 90
Ignite 80
Ignite 70
Ignite 60
View profile
smacdonald2008
- Adobe Experience Manager
thanks for posting the information!

Views

345

Likes

0

Replies

0
Re: Can't load jquery ui resources in AEM 6.3
Avatar
Ignite 3
Level 2
15473203
Level 2

Likes

2 likes

Total Posts

10 posts

Correct reply

1 solution
Top badges earned
Ignite 3
Give Back 5
Give Back 3
Give Back
Ignite 1
View profile
15473203
- Adobe Experience Manager
Thanks, all I had to do was allow the read permission for the anonymous user on for /libs/clientlibs/granite/jquery-ui/resources on the publish instances and it worked.

Views

567

Likes

0

Replies

0
Re: Dispatcher Caching with Apache Compression causes bad ETag header
Avatar
Ignite 3
Level 2
15473203
Level 2

Likes

2 likes

Total Posts

10 posts

Correct reply

1 solution
Top badges earned
Ignite 3
Give Back 5
Give Back 3
Give Back
Ignite 1
View profile
15473203
- Adobe Experience Manager
I guess I found out why this is happening, and it appears to be a bug with Apache 2.4 when Apache serves the file (like it would out of the dispatcher cache) it adds the ETag information with "-gzip" added to the end of the ETag. But it seems on the next request, the "-gzip" appended to the end makes Apache think the file is different since the file in the dispatcher cache has not been used gzipped yet. More discussion is at http - Apache is not sending 304 response (if mod_deflate and AddOutput...

Views

468

Likes

0

Replies

0
Re: Dispatcher is not forwarding Last-Modified header when caching is disabled
Avatar
Ignite 3
Level 2
15473203
Level 2

Likes

2 likes

Total Posts

10 posts

Correct reply

1 solution
Top badges earned
Ignite 3
Give Back 5
Give Back 3
Give Back
Ignite 1
View profile
15473203
- Adobe Experience Manager
I'm having a similar issue. I'm using Dispatcher 4.2.3 and caching the response headers, but when a cached dam asset is returned, the cached header value is not used, the last modified time of the actual cached file is still used. Any ideas? /clientheaders allows all headers.

Views

571

Likes

0

Replies

0
Likes given to
Likes from