<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Configure URL in saved search results in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Configure-URL-in-saved-search-results/m-p/101636#M26259</link>
    <description>&lt;P&gt;I solved this problem in my Apache SSO setup - Splunk e-mail alerts contained &lt;A href="http://hostname:8000/app/" rel="nofollow"&gt;http://hostname:8000/app/&lt;/A&gt; rather than &lt;A href="https://hostname/app/" rel="nofollow"&gt;https://hostname/app/&lt;/A&gt;. I was unable to convince Splunk to change its URL, but I was successful in configuring Apache to redirect the broken URLs to the correct location.&lt;/P&gt;

&lt;P&gt;First I configured Splunk to listen only on the loopback address in /usr/local/splunk/etc/system/local/web.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;server.socket_host = 127.0.0.1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then I added a VirtualHost to Apache listening on the public IP, port 8000 to redirect to the correct URL. In RHEL/CENTOS' /etc/httpd/conf.d/vhost-splunk-redirect.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Listen 192.168.0.1:8000
NameVirtualHost 192.168.0.1:8000

&amp;lt;VirtualHost 192.168.0.1:8000&amp;gt;
    RewriteEngine On
    RewriteRule .* &lt;A href="https://hostname.com%{REQUEST_URI}" target="test_blank"&gt;https://hostname.com%{REQUEST_URI}&lt;/A&gt; [R,L]
&amp;lt;/VirtualHost&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;With this configuration Splunk alert URLs redirect to their equivalent, functional SSO/SSL URLs.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Mar 2011 01:27:22 GMT</pubDate>
    <dc:creator>njdove</dc:creator>
    <dc:date>2011-03-23T01:27:22Z</dc:date>
    <item>
      <title>Configure URL in saved search results</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Configure-URL-in-saved-search-results/m-p/101634#M26257</link>
      <description>&lt;P&gt;I have SSO working with apache responding to a "splunk" cname. But when splunk emails search results the URL is &lt;A href="https://hostname:port/" rel="nofollow"&gt;https://hostname:port/&lt;/A&gt;... How can I configure splunk to just use a "https://splunk" url so connections will pass through apache?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Dec 2010 03:30:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Configure-URL-in-saved-search-results/m-p/101634#M26257</guid>
      <dc:creator>dmesler</dc:creator>
      <dc:date>2010-12-09T03:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: Configure URL in saved search results</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Configure-URL-in-saved-search-results/m-p/101635#M26258</link>
      <description>&lt;P&gt;In &lt;A href="http://www.splunk.com/base/Documentation/4.1.6/Admin/Alertactionsconf" rel="nofollow"&gt;alert_actions.conf&lt;/A&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;hostname=splunk.yourdomain.com
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 09 Dec 2010 05:27:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Configure-URL-in-saved-search-results/m-p/101635#M26258</guid>
      <dc:creator>southeringtonp</dc:creator>
      <dc:date>2010-12-09T05:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: Configure URL in saved search results</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Configure-URL-in-saved-search-results/m-p/101636#M26259</link>
      <description>&lt;P&gt;I solved this problem in my Apache SSO setup - Splunk e-mail alerts contained &lt;A href="http://hostname:8000/app/" rel="nofollow"&gt;http://hostname:8000/app/&lt;/A&gt; rather than &lt;A href="https://hostname/app/" rel="nofollow"&gt;https://hostname/app/&lt;/A&gt;. I was unable to convince Splunk to change its URL, but I was successful in configuring Apache to redirect the broken URLs to the correct location.&lt;/P&gt;

&lt;P&gt;First I configured Splunk to listen only on the loopback address in /usr/local/splunk/etc/system/local/web.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;server.socket_host = 127.0.0.1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then I added a VirtualHost to Apache listening on the public IP, port 8000 to redirect to the correct URL. In RHEL/CENTOS' /etc/httpd/conf.d/vhost-splunk-redirect.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Listen 192.168.0.1:8000
NameVirtualHost 192.168.0.1:8000

&amp;lt;VirtualHost 192.168.0.1:8000&amp;gt;
    RewriteEngine On
    RewriteRule .* &lt;A href="https://hostname.com%{REQUEST_URI}" target="test_blank"&gt;https://hostname.com%{REQUEST_URI}&lt;/A&gt; [R,L]
&amp;lt;/VirtualHost&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;With this configuration Splunk alert URLs redirect to their equivalent, functional SSO/SSL URLs.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Mar 2011 01:27:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Configure-URL-in-saved-search-results/m-p/101636#M26259</guid>
      <dc:creator>njdove</dc:creator>
      <dc:date>2011-03-23T01:27:22Z</dc:date>
    </item>
  </channel>
</rss>

