-
Notifications
You must be signed in to change notification settings - Fork 452
[fortinet_fortigate] Set bad URL to url.original #13767
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
Conversation
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Package fortinet_fortigate - 1.32.1 containing this change is available at https://epr.elastic.co/package/fortinet_fortigate/1.32.1/ |
Proposed commit message
Instead of causing an error when an invalid URI is processed with the
uri_parts
processor, this instead sets the value tourl.original
.This adds several example logs to test against.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots