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?

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...