[packetbeat/protos/http] fix: non-standard http host format error and add extract host tests.

[moonD4rk]

Proposed commit message

fix: non-standard http host format when packetbeat capture http request and add extract host test cases.

• Add test for extractHostHeader function

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

check and use go test -v ./...

Related issues

• Close [packetbeat] panic when parsing HTTP host header with non-standard format  #36497

Use cases

Packetbeat panic when HTTP requests that have a non-standard Host header. such as :1234

TestCase

func TestHttpParser_extractHostHeader(t *testing.T) {
	var testCases = []struct {
		host       string
		wantedHost string
		wantedPort int
	}{
		{":1234", "", 1234},
	}
	for _, tc := range testCases {
		host, port := extractHostHeader(tc.host)
		assert.Equal(t, tc.wantedHost, host)
		assert.Equal(t, tc.wantedPort, port)
	}
}

use go test -v ./...

before:

=== RUN   TestHttpParser_extractHostHeader
--- FAIL: TestHttpParser_extractHostHeader (0.00s)
panic: runtime error: index out of range [0] with length 0 [recovered]
	panic: runtime error: index out of range [0] with length 0

after:

=== RUN   TestHttpParser_extractHostHeader
--- PASS: TestHttpParser_extractHostHeader (0.00s)
PASS

Screenshots

Logs

[cla-checker-service]

💚 CLA has been signed

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @moonD4rk? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-09-05T19:21:23.673+0000

• Duration: 47 min 10 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2361
Skipped	25
Total	2386

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

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

[bhapas]

@moonD4rk

Thank you for your contribution. Can you please sign the CLA agreement for contributors for CI to proceed running your change. - Contributor Agreement

[bhapas]

/test

[moonD4rk]

@moonD4rk

Thank you for your contribution. Can you please sign the CLA agreement for contributors for CI to proceed running your change. - Contributor Agreement↳

Hi, I'm already signed and passed the CI test.

[bhapas]

Thanks @moonD4rk
Can you add a changelog after

beats/CHANGELOG-developer.next.asciidoc

Line 88 in 1209bca

- Fixed some race conditions in tests {pull}36185[36185]

[bhapas]

/test

[bhapas]

/test