Skip to content

Commit 66bd6dd

Browse files
Fix link rendering issues and usage of http in links (#2423)
- Removed link text markup, causes issues since final rendering of docs can be in either markdown or asciidoc - Replace http with https in links
1 parent 5f48aff commit 66bd6dd

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
@@ -496,7 +496,7 @@ a| The highest registered client domain, stripped of the subdomain.
496496

497497
For example, the registered domain for "foo.example.com" is "example.com".
498498

499-
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".
499+
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".
500500

501501
type: keyword
502502

@@ -532,7 +532,7 @@ example: `east`
532532

533533
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".
534534

535-
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".
535+
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".
536536

537537
type: keyword
538538

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

15971597
For example, the registered domain for "foo.example.com" is "example.com".
15981598

1599-
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".
1599+
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".
16001600

16011601
type: keyword
16021602

@@ -1632,7 +1632,7 @@ example: `east`
16321632

16331633
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".
16341634

1635-
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".
1635+
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".
16361636

16371637
type: keyword
16381638

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

21262126
For example, the registered domain for "foo.example.com" is "example.com".
21272127

2128-
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".
2128+
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".
21292129

21302130
type: keyword
21312131

@@ -2161,7 +2161,7 @@ example: `www`
21612161

21622162
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".
21632163

2164-
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".
2164+
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".
21652165

21662166
type: keyword
21672167

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

23922392
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.
23932393

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

23962396
type: keyword
23972397

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

62296229
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.
62306230

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

62336233
type: keyword
62346234

@@ -7897,7 +7897,7 @@ example: `6.3.9600.17415`
78977897

78987898
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.
78997899

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

79027902
type: keyword
79037903

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

99359935
For example, the registered domain for "foo.example.com" is "example.com".
99369936

9937-
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".
9937+
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".
99389938

99399939
type: keyword
99409940

@@ -9970,7 +9970,7 @@ example: `east`
99709970

99719971
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".
99729972

9973-
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".
9973+
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".
99749974

99759975
type: keyword
99769976

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

1050610506
For example, the registered domain for "foo.example.com" is "example.com".
1050710507

10508-
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".
10508+
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".
1050910509

1051010510
type: keyword
1051110511

@@ -10541,7 +10541,7 @@ example: `east`
1054110541

1054210542
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".
1054310543

10544-
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".
10544+
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".
1054510545

1054610546
type: keyword
1054710547

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

1280512805
For example, the registered domain for "foo.example.com" is "example.com".
1280612806

12807-
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".
12807+
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".
1280812808

1280912809
type: keyword
1281012810

@@ -12864,7 +12864,7 @@ image:https://img.shields.io/badge/OpenTelemetry-4a5ca6?style=flat&logo=opentele
1286412864

1286512865
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".
1286612866

12867-
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".
12867+
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".
1286812868

1286912869
type: keyword
1287012870

@@ -13663,7 +13663,7 @@ The vulnerability fields describe information about a vulnerability that is rele
1366313663
[[field-vulnerability-category]]
1366413664
<<field-vulnerability-category, vulnerability.category>>
1366513665

13666-
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])
13666+
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)
1366713667

1366813668
This field must be an array.
1366913669

@@ -13700,7 +13700,7 @@ example: `CVSS`
1370013700
[[field-vulnerability-description]]
1370113701
<<field-vulnerability-description, vulnerability.description>>
1370213702

13703-
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])
13703+
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)
1370413704

1370513705
type: keyword
1370613706

@@ -13738,7 +13738,7 @@ example: `CVE`
1373813738
[[field-vulnerability-id]]
1373913739
<<field-vulnerability-id, vulnerability.id>>
1374013740

13741-
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])
13741+
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)
1374213742

1374313743
type: keyword
1374413744

0 commit comments

Comments
 (0)