You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[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]>
Copy file name to clipboardExpand all lines: docs/fields/field-details.asciidoc
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -475,7 +475,7 @@ a| The highest registered client domain, stripped of the subdomain.
475
475
476
476
For example, the registered domain for "foo.example.com" is "example.com".
477
477
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".
479
479
480
480
type: keyword
481
481
@@ -511,7 +511,7 @@ example: `east`
511
511
512
512
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".
513
513
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".
515
515
516
516
type: keyword
517
517
@@ -1537,7 +1537,7 @@ a| The highest registered destination domain, stripped of the subdomain.
1537
1537
1538
1538
For example, the registered domain for "foo.example.com" is "example.com".
1539
1539
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".
1541
1541
1542
1542
type: keyword
1543
1543
@@ -1573,7 +1573,7 @@ example: `east`
1573
1573
1574
1574
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".
1575
1575
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".
1577
1577
1578
1578
type: keyword
1579
1579
@@ -2056,7 +2056,7 @@ a| The highest registered domain, stripped of the subdomain.
2056
2056
2057
2057
For example, the registered domain for "foo.example.com" is "example.com".
2058
2058
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".
2060
2060
2061
2061
type: keyword
2062
2062
@@ -2092,7 +2092,7 @@ example: `www`
2092
2092
2093
2093
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".
2094
2094
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".
2096
2096
2097
2097
type: keyword
2098
2098
@@ -2320,7 +2320,7 @@ Note: this field should contain an array of values.
2320
2320
2321
2321
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.
2322
2322
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
2324
2324
2325
2325
type: keyword
2326
2326
@@ -6035,7 +6035,7 @@ beta::[ These fields are in beta and are subject to change.]
6035
6035
6036
6036
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.
6037
6037
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
6039
6039
6040
6040
type: keyword
6041
6041
@@ -7688,7 +7688,7 @@ example: `6.3.9600.17415`
7688
7688
7689
7689
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.
7690
7690
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
7692
7692
7693
7693
type: keyword
7694
7694
@@ -9693,7 +9693,7 @@ a| The highest registered server domain, stripped of the subdomain.
9693
9693
9694
9694
For example, the registered domain for "foo.example.com" is "example.com".
9695
9695
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".
9697
9697
9698
9698
type: keyword
9699
9699
@@ -9729,7 +9729,7 @@ example: `east`
9729
9729
9730
9730
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".
9731
9731
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".
9733
9733
9734
9734
type: keyword
9735
9735
@@ -10252,7 +10252,7 @@ a| The highest registered source domain, stripped of the subdomain.
10252
10252
10253
10253
For example, the registered domain for "foo.example.com" is "example.com".
10254
10254
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".
10256
10256
10257
10257
type: keyword
10258
10258
@@ -10288,7 +10288,7 @@ example: `east`
10288
10288
10289
10289
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".
10290
10290
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".
10292
10292
10293
10293
type: keyword
10294
10294
@@ -12477,7 +12477,7 @@ a| The highest registered url domain, stripped of the subdomain.
12477
12477
12478
12478
For example, the registered domain for "foo.example.com" is "example.com".
12479
12479
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".
12481
12481
12482
12482
type: keyword
12483
12483
@@ -12531,7 +12531,7 @@ example: `east`
12531
12531
12532
12532
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".
12533
12533
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".
12535
12535
12536
12536
type: keyword
12537
12537
@@ -13310,7 +13310,7 @@ The vulnerability fields describe information about a vulnerability that is rele
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)
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)
13351
13351
13352
13352
type: keyword
13353
13353
@@ -13385,7 +13385,7 @@ example: `CVE`
13385
13385
[[field-vulnerability-id]]
13386
13386
<<field-vulnerability-id, vulnerability.id>>
13387
13387
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)
0 commit comments