Fortinet FortiGate WebSession Parsers Parsing Fix & Additions#10865
Fortinet FortiGate WebSession Parsers Parsing Fix & Additions#10865t-pol wants to merge 49 commits intoAzure:masterfrom
Conversation
|
@microsoft-github-policy-service agree |
|
Hi @t-pol, |
|
Hi @t-pol, |
|
The issues have been fixed. Thanks |
|
Thanks @t-pol. |
|
Hello, is there any feedback regarding the parser ? |
|
can you please add tester files after testing |
|
Hi @t-pol, please check above comments from @Alekhya0824 and act accordingly. Thanks |
|
Hi @t-pol, |
|
Hello, |
|
@t-pol Thankyou for your updates. Can we try below?
|
|
Changes have been applied. |
|
Hi @t-pol, |
|
Hi @t-pol, |
|
Hello @v-atulyadav , I have fixed the pending issues. Please proceed and check the pr. |
|
Hello @v-atulyadav @vakohl , I have fixed the pending issues. Please proceed and check the pr. |
|
Hi @t-pol, |
|
It is not an error to the parser or the changes that i have performed. Please check the relevant error. |
|
Closing this PR, as same changes are being done using different PR. |
Required items, please complete
Change(s):
Reason for Change(s):
When there is no User Agent string in AdditionalExtensions, the parsing of HttpRequestMethod fails.

Incorrect parsing of HttpRequestMethod and HttpUserAgent.
Adding NetworkApplicationProtocol field in the project-rename. (Optional field in the parser, but it exists in FortiGate logs)
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present: