Hi all, We are running the latest version of URL Toolbox (at the time of writing, 1.9.1 released on Dec 2021) on Splunk 8.2.3 with Splunk ES 6.6.2. After the upgrade, we have noticed that the mozilla list is not working properly anymore. To test it: | makeresults | eval domain="http://www.example.com/123/123.php",list="mozilla" | `ut_parse_extended(domain,list)` Gives: domain list ut_domain ut_domain_without_tld ut_fragment ut_netloc ut_params ut_path ut_port ut_query ut_scheme ut_subdomain ut_subdomain_count ut_tld http://www.example.com/123/123.php mozilla None None None www.example.com None /123/123.php 80 None http None 0 None With iana no problems at all (even if the parsing is a bit different and mozilla would be the ideal ones for our user cases): | makeresults | eval domain="http://www.example.com/123/123.php",list="iana" | `ut_parse_extended(domain,list)`   domain list ut_domain ut_domain_without_tld ut_fragment ut_netloc ut_params ut_path ut_port ut_query ut_scheme ut_subdomain ut_subdomain_count ut_subdomain_level_1 ut_tld http://www.example.com/123/123.php iana example.com example None www.example.com None /123/123.php 80 None http www 1 www com   Is anyone having the same issue and/or a fix that we might apply? Thank you and cheers! ... View more

Hi team, I am running the latest Hurricane Labs Shodan version 2.0.8, but I am getting this error when running the saved search: 03-04-2021 13:50:53.754 ERROR KVStoreLookup - KV Store output failed with err: The _id field is a reserved field and may not be present in a document or query. message: 03-04-2021 13:50:53.755 ERROR SearchResultsFiles - An error occurred while saving to the KV Store. Look at search.log for more information. 03-04-2021 13:50:53.755 ERROR outputcsv - sid:1614865793.691 Could not write to collection 'shodan_output': An error occurred while saving to the KV Store. Look at search.log for more information.. It looks like that, somehow, an _id field is being generated from the search I could rename it of course, but I do not know how it is going to impact the rest of the app without troubleshooting it so I was wondering, how can I fix it quickly and, eventually, get the app updated to prevent such error on the next iterations? Thanks and regards! ... View more