<?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 Problem with HTTP request parameters in FirePower log messages in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/problem-with-http-request-parameters-in-firepower-log-messages/m-p/3307243#M1064720</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example we make a HTTP(S) request through FirePower, something like this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;GET test.site.com/search?text=TEST&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;however URL field in log line will contain only test.site.com, without request parameters or even a path. But in next requests we will see our full request in Referer field)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there is way to fix this? Since many other firewalls, proxies, UTMs handle this properly, I hope that should be a solution.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 15:05:11 GMT</pubDate>
    <dc:creator>bob.jensen</dc:creator>
    <dc:date>2020-02-21T15:05:11Z</dc:date>
    <item>
      <title>Problem with HTTP request parameters in FirePower log messages</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-http-request-parameters-in-firepower-log-messages/m-p/3307243#M1064720</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example we make a HTTP(S) request through FirePower, something like this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;GET test.site.com/search?text=TEST&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;however URL field in log line will contain only test.site.com, without request parameters or even a path. But in next requests we will see our full request in Referer field)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there is way to fix this? Since many other firewalls, proxies, UTMs handle this properly, I hope that should be a solution.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:05:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-http-request-parameters-in-firepower-log-messages/m-p/3307243#M1064720</guid>
      <dc:creator>bob.jensen</dc:creator>
      <dc:date>2020-02-21T15:05:11Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with HTTP request parameters in FirePower log messages</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-http-request-parameters-in-firepower-log-messages/m-p/3308252#M1064721</link>
      <description>&lt;P&gt;Hi Bob,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope you are doing good.&lt;/P&gt;
&lt;P&gt;Please clarify that what exactly you want to achive.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1 -Do you wanna see every detail in log line (i.e. along with the request parameters and path ) OR&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2 - You dont wanna see " full request in Referer field"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answering the first concern, Firepower make use of pre-processors, which are used to normalize traffic of each protocol and then forward it for inspection to the inspection engine, so that it becomes smooth for inspection engine to inspect the traffic. So I belive, if you are see the HTTP request traffic in the manner you described, it shall be due to pre-processor behaviour.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am also curious to know that this how is this behaviour is leading any problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Br&lt;/P&gt;
&lt;P&gt;Shivdbe&lt;/P&gt;
&lt;P&gt;EX Cisco-TAC&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2018 12:32:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-http-request-parameters-in-firepower-log-messages/m-p/3308252#M1064721</guid>
      <dc:creator>er.shivamdubey31190</dc:creator>
      <dc:date>2018-01-09T12:32:44Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with HTTP request parameters in FirePower log messages</title>
      <link>https://community.cisco.com/t5/network-security/problem-with-http-request-parameters-in-firepower-log-messages/m-p/3308419#M1064722</link>
      <description>&lt;P&gt;Thank you for reply.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I want to see full HTTP(S) GET request URL with parameters. For example we have request like this:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://site.com/search/?query=MY+REQUEST" target="_blank"&gt;https://site.com/search/?query=MY+REQUEST&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is how it looks like in Squid log(with HTTPS inspection):&lt;/P&gt;
&lt;P&gt;1515252780.448&amp;nbsp; &amp;nbsp; 786 192.168.0.233 TCP_MISS/200 67620 GET &lt;A href="https://site.com/search/" target="_blank"&gt;https://site.com/search/&lt;/A&gt;? - HIER_DIRECT/- text/html /search/?query=MY+REQUEST 1311 ""&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;as you can see there is a separate field with URL path and parameters, however it can be configured to store whole URL in one field.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With FirePower I cant achieve this, I get only domain name in URL field in log messages, i.e. in the example above I will get only this:&lt;/P&gt;
&lt;P&gt;URL: &lt;A href="https://site.com" target="_blank"&gt;https://site.com&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;PS: In FirePower I have configured SSL policy with Decrypt - Resign action.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2018 16:36:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-with-http-request-parameters-in-firepower-log-messages/m-p/3308419#M1064722</guid>
      <dc:creator>bob.jensen</dc:creator>
      <dc:date>2018-01-09T16:36:29Z</dc:date>
    </item>
  </channel>
</rss>

