On thing you might want to add is blocking direct access to the Splunk webserver on port 8000. Otherwise there is no point in setting up a proxy.

Ya, this is what I did too, just never placed it into this article. I just proxied it and disabled port 8000 from the outside.

On thing you might want to add is blocking direct access to the Splunk webserver on port 8000. Otherwise there is no point in setting up a proxy.

I used iptables rules as follows:

# Block all requests to port 8000
iptables -I INPUT -p tcp –dport 8000 -j REJECT

# Allow requests to port 8000 from localhost
iptables -I INPUT -s 127.0.0.1/32 -p tcp –dport 8000 -j ACCEPT

Nice read. Thnx for the detailed write-up.

Thanks for the kinda words. Feel free to send me other ideas. I have plenty more to come, actually, but I’ve been rather busy. I’ll see if I can get some of my ideas off the paper and onto the site.

Thanks,
Drew

This can easily be due to Apache configuration, that is probably not due to my little tutorial here. I make sure all of my articles are pretty straight forward and very wordy to insure that I get all the detail out.

What OS are you running, and what version of Apache? If you could contact me via the Contact Me page with your Apache configuration, I might be able to help you. Internal Server Errors (500) are usually due to a configuration on the actual web server, and might not be due to my article, especially since you stated that you get the password prompt, and once it lets you in, it gives you internal server errors. This statement actually indicates that my article deemed a success and it did work.

Please let me know how I can further help you out with these errors. Drop me a line or something; I’d love to help.

Regards,
Drew

Thanks for the how-to, anyway ;)

Either way, its a great way of password protecting directories, without having root access to the server.

Again, thanks!