<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Splunk with SSL and Password Protection Using Apache</title>
	<atom:link href="http://www.laneolson.ca/2009/07/08/splunk-with-ssl-and-password-protection-using-apache/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.laneolson.ca/2009/07/08/splunk-with-ssl-and-password-protection-using-apache/</link>
	<description></description>
	<lastBuildDate>Thu, 06 Jan 2011 20:30:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lane</title>
		<link>http://www.laneolson.ca/2009/07/08/splunk-with-ssl-and-password-protection-using-apache/comment-page-1/#comment-2114</link>
		<dc:creator>Lane</dc:creator>
		<pubDate>Tue, 13 Apr 2010 15:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.laneolson.ca/?p=90#comment-2114</guid>
		<description>Good point nj, I never thought of doing it that way.  Thanks for the tip!</description>
		<content:encoded><![CDATA[<p>Good point nj, I never thought of doing it that way.  Thanks for the tip!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nj</title>
		<link>http://www.laneolson.ca/2009/07/08/splunk-with-ssl-and-password-protection-using-apache/comment-page-1/#comment-2109</link>
		<dc:creator>nj</dc:creator>
		<pubDate>Tue, 13 Apr 2010 02:03:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.laneolson.ca/?p=90#comment-2109</guid>
		<description>Hey, thanks for this help. 

Another option than using the firewall to protect port 8000 is to have spunk listen on 127.0.0.1 (using SPLUNK_BINDIP in splunk-launch.conf) only, and use ProxyPass and ProxyPassReverse in the virtual host directive to redirect connections to port 443 to 8000.</description>
		<content:encoded><![CDATA[<p>Hey, thanks for this help. </p>
<p>Another option than using the firewall to protect port 8000 is to have spunk listen on 127.0.0.1 (using SPLUNK_BINDIP in splunk-launch.conf) only, and use ProxyPass and ProxyPassReverse in the virtual host directive to redirect connections to port 443 to 8000.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lane</title>
		<link>http://www.laneolson.ca/2009/07/08/splunk-with-ssl-and-password-protection-using-apache/comment-page-1/#comment-1678</link>
		<dc:creator>Lane</dc:creator>
		<pubDate>Tue, 19 Jan 2010 21:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.laneolson.ca/?p=90#comment-1678</guid>
		<description>Hey Massimo, I may have to take a look at your apache configuration files.   Here are a few things to check first:

1. Have you enabled SSL on your splunk installation (in the admin/manager section)? 

2.  What happens when you go to https://machine.mydomain:8000/ (you may have to disable the firewall rules first) 

If you&#039;re still having problems post the apache config file so I can take a look at it.

- Lane</description>
		<content:encoded><![CDATA[<p>Hey Massimo, I may have to take a look at your apache configuration files.   Here are a few things to check first:</p>
<p>1. Have you enabled SSL on your splunk installation (in the admin/manager section)? </p>
<p>2.  What happens when you go to <a href="https://machine.mydomain:8000/" rel="nofollow">https://machine.mydomain:8000/</a> (you may have to disable the firewall rules first) </p>
<p>If you&#8217;re still having problems post the apache config file so I can take a look at it.</p>
<p>- Lane</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Massimo</title>
		<link>http://www.laneolson.ca/2009/07/08/splunk-with-ssl-and-password-protection-using-apache/comment-page-1/#comment-1615</link>
		<dc:creator>Massimo</dc:creator>
		<pubDate>Tue, 12 Jan 2010 16:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.laneolson.ca/?p=90#comment-1615</guid>
		<description>Hi! I followed your guide but when I can try to access to https://machine.mydomain:443/ and digit user/pass I receive message &quot;Bad Gateway
The proxy server received an invalid response from an upstream server&quot; Can you help me please? Thank you!</description>
		<content:encoded><![CDATA[<p>Hi! I followed your guide but when I can try to access to <a href="https://machine.mydomain:443/" rel="nofollow">https://machine.mydomain:443/</a> and digit user/pass I receive message &#8220;Bad Gateway<br />
The proxy server received an invalid response from an upstream server&#8221; Can you help me please? Thank you!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

