Security

Is there a recent change in Splunk that caused the proxy settings in server.conf to change?

Volto
Path Finder

Hello,

I was wondering if there was a recent change in Splunk that caused the proxy settings in server.conf to change.

We've recently installed a fresh version of Splunk 7.0.2, and we noticed a large amount of proxy requests for the localhost of the Splunk box over the internal Splunk port of 8089.

Looking through the docs; http://docs.splunk.com/Documentation/Splunk/7.0.2/Admin/Serverconf#Splunkd_http_proxy_configuration, it says that the no_proxy configuration is set to localhost and 127.0.0.1 by default.

Looking through the default server.conf on our installation I don't see the no_proxy setting set.

Has anyone else seen this behavior with their Splunk installation?

Volto
Path Finder

After setting the no_proxy setting in server.conf Splunk looks like it's still attempting to use the proxy to connect to localhost.

Looking in the documentation it has the addresses wrapped in double quotes, is that needed for the no_proxy setting?

0 Karma
Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...