Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate Performant XML Identification #22965

Closed
andrewstucki opened this issue Dec 7, 2020 · 2 comments
Closed

Investigate Performant XML Identification #22965

andrewstucki opened this issue Dec 7, 2020 · 2 comments

Comments

@andrewstucki
Copy link

Describe the enhancement:

#22940 adds code for mime type sniffing. Currently, if an xml document doesn't begin with an <?xml signature the way the code determines if it's xml is by unmarshaling everything and seeing if an error occurred. Go's xml implementation is pretty bad in terms of speed and memory pressure. We should replace this with a more scalable implementation. See #22940 (comment) for some ideas for identification rules for an XML document.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@jlind23
Copy link
Collaborator

jlind23 commented Apr 5, 2022

Backlog grooming: Closing it for now until further activity.

@jlind23 jlind23 closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants