Security

server.conf crossOriginSharingPolicy url format

BernardEAI
Communicator

I'm trying to set up some HTTP Origins for which to return Access-Control-Allow-* (CORS) headers. According to the Splunk documentation, I need to add these to the [httpServer] stanza of the server.conf file, under the crossOriginSharingPolicy heading. I'm getting a problem when the url has a slash in it, like:

https://address.test.frontend.aws.cloud/network

Splunk raises an error during server start, with the following message:

ValueError: invalid literal for int() with base 10

I think the issue is due to the slash in the url, I tested removing the /network part and the server started fine.

 

 

Labels (1)
Tags (1)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

Why do you need the /network part - shouldn't this just be a server address rather than access path?

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust

Why do you need the /network part - shouldn't this just be a server address rather than access path?

Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf24, and Community Connections

Thank you to everyone in the Splunk Community who joined us for .conf24 – starting with Splunk University and ...

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

 (view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...