Skip to content

[Fortinet Fortiproxy] URL Field Parsing Errors #19603

Open
robester0403 wants to merge 3 commits into
elastic:mainfrom
robester0403:fortinet-fortiproxy-url-parsing-issue
Open

[Fortinet Fortiproxy] URL Field Parsing Errors #19603
robester0403 wants to merge 3 commits into
elastic:mainfrom
robester0403:fortinet-fortiproxy-url-parsing-issue

Conversation

@robester0403

@robester0403 robester0403 commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Proposed commit message

Fix URI parsing failures when url field contains only a path or query string.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
    - [ ] I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
    - [ ] I have verified that Kibana version constraints are current according to guidelines.
    - [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

Resolves: #15111

Screenshots

image

…es on bare-path and special-character url fields
@robester0403 robester0403 requested a review from a team as a code owner June 17, 2026 15:17
@robester0403 robester0403 added bugfix Pull request that fixes a bug issue Integration:fortinet_fortiproxy Fortinet FortiProxy Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience] labels Jun 17, 2026
@robester0403 robester0403 self-assigned this Jun 17, 2026
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

Pinging @elastic/integration-experience (Team:Integration-Experience)

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Jun 17, 2026

Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

Co-authored-by: Cursor <cursoragent@cursor.com>
@robester0403 robester0403 force-pushed the fortinet-fortiproxy-url-parsing-issue branch from 5283dfe to 923bd46 Compare June 17, 2026 15:58
Comment thread packages/fortinet_fortiproxy/changelog.yml Outdated
field: client.ip
if: ctx._fields_.clientip != null

- script:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the Painless script is necessary as you can also use the set processors to reconstruct the URL:

- set: temp.scheme <- url.scheme / network.protocol
- set: temp.url <- fields.url        # if already http(s)://
- set: temp.url <- {{scheme}}://{{url.domain}}{{fields.url}}
...

String scheme;
if (ctx.url?.scheme != null) { scheme = ctx.url.scheme.toString().toLowerCase(); }
else if (['http','https'].contains(ctx.network?.protocol)) { scheme = ctx.network.protocol; }
else if (ctx.server?.port instanceof Number && ctx.server.port == 443) { scheme = 'https'; }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wary of special-casing 443 as HTTPS may very well be using a different port. Note there are no instances of ctx.server.port == 443 string in the current integrations codebase.

Perhaps the scheme will in fact be always present in these cases so we don't need to guess?

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown

✅ All changelog entries have the correct PR link.

@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

History

cc @robester0403

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Pull request that fixes a bug issue Integration:fortinet_fortiproxy Fortinet FortiProxy Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Fortinet Fortiproxy]: Fortinet Fortiproxy Integration does not correctly parse URL

3 participants