I have the same requirement from Customer. The affinity cookie has no "Secure" attribute. I set "org.apache.felix.http" config as blow. "org.apache.felix.https.jetty.session.cookie.secure": trueAlso try to edit cookies on the dispatcher but that didn't work either. Header always edit Set-Cookie ^(.*...

Yes, you are right. I added extra query logging on test environment and found out there is a misnamed index on publish instance.  In the beginning of project, i had created a custom index without checking naming convention for AEM Cloud. Later, i had raised a ticket and support team removed it from ...

I tested on Microsoft Edge instead of Chrome and there is no difference. My search result page url like this : https://{publish_address}/personal/search.html?q=space&p=personaland search result servlet url is like that:/content/abc/en/personal/search/jcr:content/.../searchresult.search.personal.0.js...

I have a servlet that call query api and returns the result and it doesn't cache. Also call the search result page with "keyword" query parameter, so the search result page is not cached 

Hi Everyone, I created a custom lucene index on local environment and deploy it to the cloud via ui.apps module. Index definition created on Author instance succesfully. Then i created new version of the index with naming convention. first index name "cqPageLucene-custom-1" and new one's name is "cq...

As far as I understood, there isn't a way to Power User manages the rewrite rules. Rewrite rules have to be under dispatcher conf and deployed via pipeline, right? 

Hi, We have added our customer old redirection rules in conf.d/rewrites/rewrites.rules file. But every time we need to add a new rule, we need to update our code and have to do deployment on production site. We don't want to do deployment frequently just for the rewrite rules and customer wants to m...

Hi everyone, We need to do same redirection (non-WWW to WWW) on our cloud environment. But we did content path masking via Apache Sling Resource Resolver Factory configuration. We didn't create any mapping under /etc/map.. path. Our prod environment have 2 DNS record. One for www , one for non-www. ...

That does the trick, thanks 

I also added "scheduler.concurrent=false" property. Same as "runOn=Leader" property, my scheduled job do not trigger even once. I checked my job via Developer Console and it's state is Active as below. Did i miss something? {"name": "com.*******.core.schedulers.TestScheduledTask","bundle": {"bundleI...