<?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: How to find the redirect request along with its redirected target location? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199581#M187518</link>
    <description>&lt;P&gt;One information that can be the same between these two requests can be the client (source) ip. So if the ip remains the same between the original request and the redirected request, how would I map both?&lt;/P&gt;</description>
    <pubDate>Wed, 26 Mar 2014 19:02:51 GMT</pubDate>
    <dc:creator>santhakr</dc:creator>
    <dc:date>2014-03-26T19:02:51Z</dc:date>
    <item>
      <title>How to find the redirect request along with its redirected target location?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199577#M187514</link>
      <description>&lt;P&gt;When a request comes on domain 1 (say abc.com) we do a 301 redirect to domain 2 (def.com). These will be two separate requests on my server access log. The original one (abc.com) ending up in 301 and the redirected one (def.com) ending up in 200 and both these requests are not synchronous or sequential.&lt;/P&gt;

&lt;P&gt;How do I write a query to find the requests on the domain 1 (abc.com) which has redirected to domain 2 (def.com). I basically want to write something below:&lt;/P&gt;

&lt;P&gt;domain="abc.com" http_status="301" response_location="def.com"&lt;/P&gt;

&lt;P&gt;I don't think there is any response location identifier in splunk or is there one? Any help would be appreciated.&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:14:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199577#M187514</guid>
      <dc:creator>santhakr</dc:creator>
      <dc:date>2020-09-28T16:14:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to find the redirect request along with its redirected target location?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199578#M187515</link>
      <description>&lt;P&gt;Do you have session IDs or cookies in your logs?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2014 18:37:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199578#M187515</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-03-26T18:37:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to find the redirect request along with its redirected target location?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199579#M187516</link>
      <description>&lt;P&gt;Nope, we didn't capture those information in the access log. Moreover the requests can be made by clients on headless mode too, which doesn't retain session information between requests.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2014 18:47:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199579#M187516</guid>
      <dc:creator>santhakr</dc:creator>
      <dc:date>2014-03-26T18:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to find the redirect request along with its redirected target location?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199580#M187517</link>
      <description>&lt;P&gt;Okay, any other info to tie the two events together?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2014 18:50:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199580#M187517</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-03-26T18:50:25Z</dc:date>
    </item>
    <item>
      <title>Re: How to find the redirect request along with its redirected target location?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199581#M187518</link>
      <description>&lt;P&gt;One information that can be the same between these two requests can be the client (source) ip. So if the ip remains the same between the original request and the redirected request, how would I map both?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2014 19:02:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199581#M187518</guid>
      <dc:creator>santhakr</dc:creator>
      <dc:date>2014-03-26T19:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to find the redirect request along with its redirected target location?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199582#M187519</link>
      <description>&lt;P&gt;You can try using transaction over clientip.&lt;/P&gt;

&lt;P&gt;your base search | transaction clientip startswith=http_status=301 endswith=http_status=200 maxevents=2&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:14:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-to-find-the-redirect-request-along-with-its-redirected/m-p/199582#M187519</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2020-09-28T16:14:35Z</dc:date>
    </item>
  </channel>
</rss>

