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!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...