Doc: Fix external links (#17288)

Author: colleenmcginnis

docs/extend/codec-new-plugin.md

@@ -305,7 +305,7 @@ Deprecations are noted in the `logstash-deprecation.log` file in the `log` direc
 Gemfiles allow Ruby’s Bundler to maintain the dependencies for your plugin. Currently, all we’ll need is the Logstash gem, for testing, but if you require other gems, you should add them in here.
 
 ::::{tip}
-See [Bundler’s Gemfile page](http://bundler.io/gemfile.md) for more details.
+See [Bundler’s Gemfile page](http://bundler.io/gemfile.html) for more details.
 ::::
 
 

docs/extend/filter-new-plugin.md

@@ -306,7 +306,7 @@ Deprecations are noted in the `logstash-deprecation.log` file in the `log` direc
 Gemfiles allow Ruby’s Bundler to maintain the dependencies for your plugin. Currently, all we’ll need is the Logstash gem, for testing, but if you require other gems, you should add them in here.
 
 ::::{tip}
-See [Bundler’s Gemfile page](http://bundler.io/gemfile.md) for more details.
+See [Bundler’s Gemfile page](http://bundler.io/gemfile.html) for more details.
 ::::
 
 

docs/extend/input-new-plugin.md

@@ -346,7 +346,7 @@ Deprecations are noted in the `logstash-deprecation.log` file in the `log` direc
 Gemfiles allow Ruby’s Bundler to maintain the dependencies for your plugin. Currently, all we’ll need is the Logstash gem, for testing, but if you require other gems, you should add them in here.
 
 ::::{tip}
-See [Bundler’s Gemfile page](http://bundler.io/gemfile.md) for more details.
+See [Bundler’s Gemfile page](http://bundler.io/gemfile.html) for more details.
 ::::
 
 

docs/extend/output-new-plugin.md

@@ -263,7 +263,7 @@ Deprecations are noted in the `logstash-deprecation.log` file in the `log` direc
 Gemfiles allow Ruby’s Bundler to maintain the dependencies for your plugin. Currently, all we’ll need is the Logstash gem, for testing, but if you require other gems, you should add them in here.
 
 ::::{tip}
-See [Bundler’s Gemfile page](http://bundler.io/gemfile.md) for more details.
+See [Bundler’s Gemfile page](http://bundler.io/gemfile.html) for more details.
 ::::
 
 

docs/reference/event-dependent-configuration.md

@@ -59,7 +59,7 @@ output {
 
 Similarly, you can convert the UTC timestamp in the `@timestamp` field into a string.
 
-Instead of specifying a field name inside the curly braces, use the `%{{FORMAT}}` syntax where `FORMAT` is a [java time format](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/format/DateTimeFormatter.md#patterns).
+Instead of specifying a field name inside the curly braces, use the `%{{FORMAT}}` syntax where `FORMAT` is a [java time format](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/format/DateTimeFormatter.html#patterns).
 
 For example, if you want to use the file output to write logs based on the event’s UTC date and hour and the `type` field:
 
@@ -72,7 +72,7 @@ output {
 ```
 
 ::::{note}
-The sprintf format continues to support [deprecated joda time format](http://joda-time.sourceforge.net/apidocs/org/joda/time/format/DateTimeFormat.md) strings as well using the `%{+FORMAT}` syntax. These formats are not directly interchangeable, and we advise you to begin using the more modern Java Time format.
+The sprintf format continues to support [deprecated joda time format](http://joda-time.sourceforge.net/apidocs/org/joda/time/format/DateTimeFormat.html) strings as well using the `%{+FORMAT}` syntax. These formats are not directly interchangeable, and we advise you to begin using the more modern Java Time format.
 ::::
 
 

docs/reference/getting-started-with-logstash.md

@@ -23,7 +23,7 @@ This section includes the following topics:
 * Java 17 (default). Check out [Using JDK 17](#jdk17-upgrade) for settings info.
 * Java 21
 
-Use the [official Oracle distribution](http://www.oracle.com/technetwork/java/javase/downloads/index.md) or an open-source distribution, such as [OpenJDK](http://openjdk.java.net/). See the [Elastic Support Matrix](https://www.elastic.co/support/matrix#matrix_jvm) for the official word on supported versions across releases.
+Use the [official Oracle distribution](http://www.oracle.com/technetwork/java/javase/downloads/index.html) or an open-source distribution, such as [OpenJDK](http://openjdk.java.net/). See the [Elastic Support Matrix](https://www.elastic.co/support/matrix#matrix_jvm) for the official word on supported versions across releases.
 
 ::::{admonition} Bundled JDK
 :class: note

docs/reference/logging.md

@@ -18,7 +18,7 @@ You can configure logging using the `log4j2.properties` file or the Logstash API
 
 ## Log4j2 configuration [log4j2]
 
-Logstash ships with a `log4j2.properties` file with out-of-the-box settings, including logging to console. You can modify this file to change the rotation policy, type, and other [log4j2 configuration](https://logging.apache.org/log4j/2.x/manual/configuration.md#Loggers).
+Logstash ships with a `log4j2.properties` file with out-of-the-box settings, including logging to console. You can modify this file to change the rotation policy, type, and other [log4j2 configuration](https://logging.apache.org/log4j/2.x/manual/configuration.html#Loggers).
 
 You must restart Logstash to apply any changes that you make to this file. Changes to `log4j2.properties` persist after Logstash is restarted.
 

docs/reference/plugins-filters-aggregate.md

@@ -373,7 +373,7 @@ Available variables are:
 
 `event`: current Logstash event
 
-`map`: aggregated map associated to `task_id`, containing key/value pairs. Data structure is a ruby [Hash](http://ruby-doc.org/core-1.9.1/Hash.md)
+`map`: aggregated map associated to `task_id`, containing key/value pairs. Data structure is a ruby [Hash](http://ruby-doc.org/core-1.9.1/Hash.html)
 
 `map_meta`: meta informations associated to aggregate map. It allows to set a custom `timeout` or `inactivity_timeout`. It allows also to get `creation_timestamp`, `lastevent_timestamp` and `task_id`.
 
@@ -406,7 +406,7 @@ To create additional events during the code execution, to be emitted immediately
     }
 ```
 
-The parameter of the function `new_event_block.call` must be of type `LogStash::Event`. To create such an object, the constructor of the same class can be used: `LogStash::Event.new()`. `LogStash::Event.new()` can receive a parameter of type ruby [Hash](http://ruby-doc.org/core-1.9.1/Hash.md) to initialize the new event fields.
+The parameter of the function `new_event_block.call` must be of type `LogStash::Event`. To create such an object, the constructor of the same class can be used: `LogStash::Event.new()`. `LogStash::Event.new()` can receive a parameter of type ruby [Hash](http://ruby-doc.org/core-1.9.1/Hash.html) to initialize the new event fields.
 
 
 ### `end_of_task` [plugins-filters-aggregate-end_of_task]

docs/reference/plugins-filters-date.md

@@ -193,7 +193,7 @@ Z
     :   Timezone offset structured as HH:mm (colon in between hour and minute offsets). Example: `-07:00`.
 
     ZZZ
-    :   Timezone identity. Example: `America/Los_Angeles`. Note: Valid IDs are listed on the [Joda.org available time zones page](http://joda-time.sourceforge.net/timezones.md).
+    :   Timezone identity. Example: `America/Los_Angeles`. Note: Valid IDs are listed on the [Joda.org available time zones page](http://joda-time.sourceforge.net/timezones.html).
 
 
 z
@@ -227,7 +227,7 @@ E
 
 For non-formatting syntax, you’ll need to put single-quote characters around the value. For example, if you were parsing ISO8601 time, "2015-01-01T01:12:23" that little "T" isn’t a valid time format, and you want to say "literally, a T", your format would be this: "yyyy-MM-dd’T’HH:mm:ss"
 
-Other less common date units, such as era (G), century (C), am/pm (a), and # more, can be learned about on the [joda-time documentation](http://www.joda.org/joda-time/key_format.md).
+Other less common date units, such as era (G), century (C), am/pm (a), and # more, can be learned about on the [joda-time documentation](http://www.joda.org/joda-time/key_format.html).
 
 
 ### `tag_on_failure` [plugins-filters-date-tag_on_failure]
@@ -251,7 +251,7 @@ Store the matching timestamp into the given target field.  If not provided, defa
 * Value type is [string](/reference/configuration-file-structure.md#string)
 * There is no default value for this setting.
 
-Specify a time zone canonical ID to be used for date parsing. The valid IDs are listed on the [Joda.org available time zones page](http://joda-time.sourceforge.net/timezones.md). This is useful in case the time zone cannot be extracted from the value, and is not the platform default. If this is not specified the platform default will be used. Canonical ID is good as it takes care of daylight saving time for you For example, `America/Los_Angeles` or `Europe/Paris` are valid IDs. This field can be dynamic and include parts of the event using the `%{{field}}` syntax
+Specify a time zone canonical ID to be used for date parsing. The valid IDs are listed on the [Joda.org available time zones page](http://joda-time.sourceforge.net/timezones.html). This is useful in case the time zone cannot be extracted from the value, and is not the platform default. If this is not specified the platform default will be used. Canonical ID is good as it takes care of daylight saving time for you For example, `America/Los_Angeles` or `Europe/Paris` are valid IDs. This field can be dynamic and include parts of the event using the `%{{field}}` syntax
 
 
 

docs/reference/plugins-filters-jdbc_static.md

@@ -447,7 +447,7 @@ name
 :   The name of the table to be created in the database.
 
 columns
-:   An array of column specifications. Each column specification is an array of exactly two elements, for example `["ip", "varchar(15)"]`. The first element is the column name string. The second element is a string that is an [Apache Derby SQL type](https://db.apache.org/derby/docs/10.14/ref/crefsqlj31068.md). The string content is checked when the local lookup tables are built, not when the settings are validated. Therefore, any misspelled SQL type strings result in errors.
+:   An array of column specifications. Each column specification is an array of exactly two elements, for example `["ip", "varchar(15)"]`. The first element is the column name string. The second element is a string that is an [Apache Derby SQL type](https://db.apache.org/derby/docs/10.14/ref/crefsqlj31068.html). The string content is checked when the local lookup tables are built, not when the settings are validated. Therefore, any misspelled SQL type strings result in errors.
 
 index_columns
 :   An array of strings. Each string must be defined in the `columns` setting. The index name will be generated internally. Unique or sorted indexes are not supported.