Hi @Nupur_Jain, thanks for the quick response, can we run AEM only on https port and not accessible on http? Will ther be any impact in using the https port in the dispatcher configuration?

We have a request from internal IT, if we can run AEM with https with out using dispatcher. currently we are accessing the aem instance using http://host:port, but they intend us to use https://host:port, what should we do to let AEM run on https on the same port?

Hi,we have already a predefined set of etc/mappings done so that both the domain can map to the content path and the path can reverse map to the domain name (which would enable shortened URL's in the live websites)PFB set configurations from crx as the screenshot and the resource resolver configs. M...

if it is at dispatcher level, we have to apply it at multiple apache instances in our design, to make this a platform level fix, we want to implement it at AEM level.

We wanted to apply HTTP OPTIONS method to be blocked in AEM, so we are using Apache sling referrer filter to add OPTIONS method, so we had to update the dav root inorder for that configuration to work.

the default configuration for the dav.root is /dav, so for a requirement we have recently changes it to /crx/repository, will there be any security issues because of this change in Apache sling simple webdav servlet? dav.create-absolute-uri=B"true"type.content="nt:resource"type.noncollections="nt:fi...

Thanks .. It worked!!

Hi Hamid, thanks for the reply, i was not able find the exact configurations which would resolve my issue. could you please help me with something specific to my issue.

so if we do the configuration in AEM to stop the OPTIONS methods, how do we test it?

We recently got a security vulnerability as below. "OPTIONS method returned values including itself" we wanted to block at AEM level using Apache Sling referrer filter by adding OPTIONS in 'filter.methods', and post updating the configurations, i was still able to get response for the below CURL req...