All Apps and Add-ons

ModInput Error: Error Processing Windows-1252 Encoded File

malvidin
Communicator

Does the Splunk Python interpreter that ModInput uses properly read/parse files that are not UTF-8 encoded?

When parsing windows-1252 encoded XML files with the TA-dmarc app, I got the following error:

validate_xml: xml parse error for file with Unsupported encoding windows-1252, line 1, column 44

However, when I parsed the file with the same scripts contained in TA-dmarc, but using the system Python interpreter, it succeeded with no errors.

An example that causes the error is available on GitHub.
https://github.com/jorritfolmer/TA-dmarc/blob/master/bin/dmarc/test/data/aol_rua.xml

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...