Deployment Architecture

Is there a way to modify Access-Control-Allow-Headers for a CORS response? (and how to get these questions actually posted?)

Marcia_Piccione
Engager

We have a client that requires at least some of the following for Access-Control-Allow-Headers:

Access-Control-Allow-Headers: origin,x-requested-with,access-control-request-headers,content-type,access-control-request-method,accept

But when Cors is enabled, splunk HEC returns:

Access-Control-Allow-Headers:Authorization

Is there a way to modify what CORS returns?

Tags (2)

derekf
Explorer

I am having the same issue. Trying to develop a webapp that leverages Splunk REST API and so far it has been a total pain.

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In January, the Splunk Threat Research Team had one release of new security content via the Splunk ES Content ...

Expert Tips from Splunk Professional Services, Ensuring Compliance, and More New ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Observability Release Update: AI Assistant, AppD + Observability Cloud Integrations & ...

This month’s releases across the Splunk Observability portfolio deliver earlier detection and faster ...