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!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...