Hi @giuseppebag, Thank you very much!

Hello Community, In our AEM setup, assets are synchronized with Dynamic Media upon activation. On the Author instance, the dam:scene7FileStatus attribute is updated to PublishComplete after activation. However, on the Publisher instance, this attribute remains as PublishIncomplete, which makes it un...

I know that this one is quite old, but just in case one faces the same issue. The Trigger Size field in Replication Agent Configuration is a batch size in bytes. So in this example the agent was constantly hitting the 1100 bytes threshold and replicating every single node.  Regards,Rustam

Hi @arunpatidar Yes, so I assume that Simple requests are not part of our use case. Thank you for your help, I really appreciate it! Regards,Rustam

I created an Adobe Support Ticket for this question and here is their response The dispatcher configuration (in the security.conf file) blocks HTTP OPTIONS requests. This rule was introduced roughly five years ago as a security measure. When the rule was implemented, blocking unsolicited HTTP method...

Thank you @ButhpurKiran !

Hi @arunpatidar , In the link you've shared, it is mentioned SpoilerApart from the headers automatically set by the user agent (for example, Connection , User-Agent , or the forbidden request headers ), the only headers which are allowed to be manually set are the CORS-safelisted request-headers , w...

Hi @arunpatidar ,I've communicated with our Dev team, and it turned out that they are already using AJAX requests rather than Fetch. Despite this, browser keeps sending preflight requests.Regards,Rustam

Hello @arunpatidar , Thank you very much for providing the resource and suggestions. I will communicate with our Dev team to explore whether switching to an AJAX request is a viable solution. We are considering a proxy setup as a last-resort solution. While I understand potential risks associated wi...

Hi @ButhpurKiran , Thank you for the quick response. After reviewing the OptionsBleed vulnerability, I noticed that according to Apache's documentation, the issue was resolved in version 2.4.28, which was released back in October 2017. However, the `security.conf` file was added in 2019 - 2 years af...