Skip to content

Commit 8552cce

Browse files
[Backport 8.x] Fix link rendering issues and usage of http in links (#2423) (#2426)
- Removed link text markup, causes issues since final rendering of docs can be in either markdown or asciidoc - Replace http with https in links Co-authored-by: Taylor Swanson <[email protected]>
1 parent 9c99db2 commit 8552cce

File tree

18 files changed

+242
-258
lines changed

18 files changed

+242
-258
lines changed

CHANGELOG.next.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ Thanks, you're awesome :-) -->
1414

1515
#### Bugfixes
1616

17+
* Fix link rendering issues and usage of http in links. #2423
18+
1719
#### Added
1820

1921
#### Improvements

docs/fields/field-details.asciidoc

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -475,7 +475,7 @@ a| The highest registered client domain, stripped of the subdomain.
475475

476476
For example, the registered domain for "foo.example.com" is "example.com".
477477

478-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
478+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
479479

480480
type: keyword
481481

@@ -511,7 +511,7 @@ example: `east`
511511

512512
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
513513

514-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
514+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
515515

516516
type: keyword
517517

@@ -1537,7 +1537,7 @@ a| The highest registered destination domain, stripped of the subdomain.
15371537

15381538
For example, the registered domain for "foo.example.com" is "example.com".
15391539

1540-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
1540+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
15411541

15421542
type: keyword
15431543

@@ -1573,7 +1573,7 @@ example: `east`
15731573

15741574
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
15751575

1576-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
1576+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
15771577

15781578
type: keyword
15791579

@@ -2056,7 +2056,7 @@ a| The highest registered domain, stripped of the subdomain.
20562056

20572057
For example, the registered domain for "foo.example.com" is "example.com".
20582058

2059-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
2059+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
20602060

20612061
type: keyword
20622062

@@ -2092,7 +2092,7 @@ example: `www`
20922092

20932093
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
20942094

2095-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
2095+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
20962096

20972097
type: keyword
20982098

@@ -2320,7 +2320,7 @@ Note: this field should contain an array of values.
23202320

23212321
a| A hash of the Go language imports in an ELF file excluding standard library imports. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values.
23222322

2323-
The algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma).
2323+
The algorithm used to calculate the Go symbol hash and a reference implementation are available here: https://github.com/elastic/toutoumomoma
23242324

23252325
type: keyword
23262326

@@ -6035,7 +6035,7 @@ beta::[ These fields are in beta and are subject to change.]
60356035

60366036
a| A hash of the Go language imports in a Mach-O file excluding standard library imports. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values.
60376037

6038-
The algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma).
6038+
The algorithm used to calculate the Go symbol hash and a reference implementation are available here: https://github.com/elastic/toutoumomoma
60396039

60406040
type: keyword
60416041

@@ -7688,7 +7688,7 @@ example: `6.3.9600.17415`
76887688

76897689
a| A hash of the Go language imports in a PE file excluding standard library imports. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values.
76907690

7691-
The algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma).
7691+
The algorithm used to calculate the Go symbol hash and a reference implementation are available here: https://github.com/elastic/toutoumomoma
76927692

76937693
type: keyword
76947694

@@ -9693,7 +9693,7 @@ a| The highest registered server domain, stripped of the subdomain.
96939693

96949694
For example, the registered domain for "foo.example.com" is "example.com".
96959695

9696-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
9696+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
96979697

96989698
type: keyword
96999699

@@ -9729,7 +9729,7 @@ example: `east`
97299729

97309730
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
97319731

9732-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
9732+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
97339733

97349734
type: keyword
97359735

@@ -10252,7 +10252,7 @@ a| The highest registered source domain, stripped of the subdomain.
1025210252

1025310253
For example, the registered domain for "foo.example.com" is "example.com".
1025410254

10255-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
10255+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
1025610256

1025710257
type: keyword
1025810258

@@ -10288,7 +10288,7 @@ example: `east`
1028810288

1028910289
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
1029010290

10291-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
10291+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
1029210292

1029310293
type: keyword
1029410294

@@ -12477,7 +12477,7 @@ a| The highest registered url domain, stripped of the subdomain.
1247712477

1247812478
For example, the registered domain for "foo.example.com" is "example.com".
1247912479

12480-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
12480+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
1248112481

1248212482
type: keyword
1248312483

@@ -12531,7 +12531,7 @@ example: `east`
1253112531

1253212532
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
1253312533

12534-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
12534+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
1253512535

1253612536
type: keyword
1253712537

@@ -13310,7 +13310,7 @@ The vulnerability fields describe information about a vulnerability that is rele
1331013310
[[field-vulnerability-category]]
1331113311
<<field-vulnerability-category, vulnerability.category>>
1331213312

13313-
a| The type of system or architecture that the vulnerability affects. These may be platform-specific (for example, Debian or SUSE) or general (for example, Database or Firewall). For example (https://qualysguard.qualys.com/qwebhelp/fo_portal/knowledgebase/vulnerability_categories.htm[Qualys vulnerability categories])
13313+
a| The type of system or architecture that the vulnerability affects. These may be platform-specific (for example, Debian or SUSE) or general (for example, Database or Firewall). For example (https://qualysguard.qualys.com/qwebhelp/fo_portal/knowledgebase/vulnerability_categories.htm)
1331413314

1331513315
This field must be an array.
1331613316

@@ -13347,7 +13347,7 @@ example: `CVSS`
1334713347
[[field-vulnerability-description]]
1334813348
<<field-vulnerability-description, vulnerability.description>>
1334913349

13350-
a| The description of the vulnerability that provides additional context of the vulnerability. For example (https://cve.mitre.org/about/faqs.html#cve_entry_descriptions_created[Common Vulnerabilities and Exposure CVE description])
13350+
a| The description of the vulnerability that provides additional context of the vulnerability. For example (https://cve.mitre.org/about/faqs.html#cve_entry_descriptions_created)
1335113351

1335213352
type: keyword
1335313353

@@ -13385,7 +13385,7 @@ example: `CVE`
1338513385
[[field-vulnerability-id]]
1338613386
<<field-vulnerability-id, vulnerability.id>>
1338713387

13388-
a| The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (https://cve.mitre.org/about/faqs.html#what_is_cve_id[Common Vulnerabilities and Exposure CVE ID])
13388+
a| The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (https://cve.mitre.org/about/faqs.html#what_is_cve_id)
1338913389

1339013390
type: keyword
1339113391

0 commit comments

Comments
 (0)