Fix destination port normalization in case of udp
This change addresses the destination port normalization in case of UDP protocol. In that if/else clause you want to populate the dst port but for doing that you check the udp_src port's existence. That said, I believe that it will not hurt in any case but it's not correct from a logical point of view: "you check the existence of a field, but then you use another field"
Can one of the admins verify this patch?
Can you add more details of why you are suggesting these changes? Also, I'll close your other PRs since we target master and backport to branches.
@suyograo about details I've updated the original comment; I hope this works for you. regards
jenkins, please test this
@vpiserchia this change looks good to me, but we'll need you to sign the CLA first! Can you visit: http://www.elasticsearch.org/contributor-agreement/ and do so?
@andrewvc I've filed the CLA
jenkins, please test this
@vpiserchia can you rebase and force push to update your branch as well? This got a little stale, it would help our build system.
Also, did you make sure to sign the CLA with the same email that's on your github account/git commits?
@andrewvc rebased against master also it uses the same email used for the CLA
This pull request does not have a backport label. Could you fix it @vpiserchia? 🙏 To fixup this pull request, you need to add the backport labels for the needed branches, such as:
backport-8./dis the label to automatically backport to the8./dbranch./dis the digit.backport-8.xis the label to automatically backport to the8.xbranch.
backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.
This pull request is now in conflicts. Could you fix it @vpiserchia? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
git fetch upstream
git checkout -b master upstream/master
git merge upstream/main
git push upstream master
not sure why I should spend time on this anymore. you have the patch, fix it