Regenerate docs with src and script changes

2025-10-16 05:28:20 +00:00 · 2025-10-13 23:32:59 +00:00 · 2025-10-13 23:32:59 +00:00 · e90d8f37f1
commit e90d8f37f1
parent dc982d9965
35 changed files with 451 additions and 451 deletions
--- a/doc/script-reference/autogenerated-packet-analyzer-index.rst
+++ b/doc/script-reference/autogenerated-packet-analyzer-index.rst
@ -93,7 +93,7 @@ Events
   Generated for ARP requests.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
   for more information about the ARP protocol.
@ -123,7 +123,7 @@ Events
   Generated for ARP replies.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
   for more information about the ARP protocol.
--- a/doc/script-reference/autogenerated-protocol-analyzer-index.rst
+++ b/doc/script-reference/autogenerated-protocol-analyzer-index.rst
--- a/doc/scripts/base/bif/plugins/Zeek_ARP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_ARP.events.bif.zeek.rst
@ -29,7 +29,7 @@ Events
   Generated for ARP replies.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
   for more information about the ARP protocol.
@ -59,7 +59,7 @@ Events
   Generated for ARP requests.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Address_Resolution_Protocol>`__
   for more information about the ARP protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_BitTorrent.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_BitTorrent.events.bif.zeek.rst
@ -44,7 +44,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see::  bittorrent_peer_cancel bittorrent_peer_choke bittorrent_peer_handshake
@ -60,7 +60,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield  bittorrent_peer_choke
@ -76,7 +76,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel
@ -92,7 +92,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -108,7 +108,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -124,7 +124,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -140,7 +140,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -156,7 +156,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -172,7 +172,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -188,7 +188,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -204,7 +204,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -220,7 +220,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -236,7 +236,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -252,7 +252,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -268,7 +268,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -284,7 +284,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -300,7 +300,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
@ -316,7 +316,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/BitTorrent_(protocol)>`__ for
   more information about the BitTorrent protocol.
   .. zeek:see:: bittorrent_peer_bitfield bittorrent_peer_cancel bittorrent_peer_choke
--- a/doc/scripts/base/bif/plugins/Zeek_DNS.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_DNS.events.bif.zeek.rst
@ -68,7 +68,7 @@ Events
   Generated for DNS replies of type *A6*. For replies with multiple answers, an
   individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -101,7 +101,7 @@ Events
   Generated for DNS replies of type *AAAA*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -134,7 +134,7 @@ Events
   Generated for DNS replies of type *A*. For replies with multiple answers, an
   individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -217,7 +217,7 @@ Events
   Generated for DNS replies of type *CNAME*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -292,7 +292,7 @@ Events
   Generated for DNS replies of type *EDNS*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -328,7 +328,7 @@ Events
   an opt-type of 10. For replies with multiple options fields, an individual event
   is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. See `RFC7873 <https://tools.ietf.org/html/rfc7873>`__ for
   more information about EDNS0 cookie. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -364,7 +364,7 @@ Events
   Generated for DNS replies of type *EDNS*. For replies with multiple options,
   an individual event is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -400,7 +400,7 @@ Events
   an opt-type of 11. For replies with multiple option fields, an individual event is
   raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. See `RFC7828 <https://tools.ietf.org/html/rfc7828>`__ for
   more information about EDNS0 TCP keepalive. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -436,7 +436,7 @@ Events
   Generated for DNS replies of type *HINFO*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -511,7 +511,7 @@ Events
   Generated for DNS replies of type *MX*. For replies with multiple answers, an
   individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -638,7 +638,7 @@ Events
   Generated for DNS replies of type *NS*. For replies with multiple answers, an
   individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -671,7 +671,7 @@ Events
   Generated for DNS replies of type *PTR*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -725,7 +725,7 @@ Events
   Generated for DNS replies of type *CNAME*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -758,7 +758,7 @@ Events
   Generated for DNS replies of type *SPF*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -791,7 +791,7 @@ Events
   Generated for DNS replies of type *SRV*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -881,7 +881,7 @@ Events
   Generated for DNS replies of type *TKEY*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. See `RFC2930 <https://tools.ietf.org/html/rfc2930>`__
   for more information about TKEY. Zeek analyzes both UDP and TCP DNS sessions.
@ -910,7 +910,7 @@ Events
   Generated for DNS replies of type *TSIG*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -945,7 +945,7 @@ Events
   Generated for DNS replies of type *TXT*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -978,7 +978,7 @@ Events
   Generated for DNS replies of type *WKS*. For replies with multiple answers,
   an individual event of the corresponding type is raised for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -1009,7 +1009,7 @@ Events
   ``dns_*`` event that will be raised for a DNS query/reply and signals that
   all resource records have been passed on.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -1035,7 +1035,7 @@ Events
   Generated for all DNS messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -1068,7 +1068,7 @@ Events
   Generated for each entry in the Question section of a DNS reply.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -1110,7 +1110,7 @@ Events
   answers to a query. Note that all of the event's parameters are parsed out of
   the reply; there's no stateful correlation with the query.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
@ -1150,7 +1150,7 @@ Events
   Generated for DNS requests. For requests with multiple queries, this event
   is raised once for each.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Domain_Name_System>`__ for more
   information about the DNS protocol. Zeek analyzes both UDP and TCP DNS
   sessions.
--- a/doc/scripts/base/bif/plugins/Zeek_FTP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_FTP.events.bif.zeek.rst
@ -29,7 +29,7 @@ Events
   Generated for server-side FTP replies.
-   See `Wikipedia <http://en.wikipedia.org/wiki/File_Transfer_Protocol>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/File_Transfer_Protocol>`__ for
   more information about the FTP protocol.
@ -57,7 +57,7 @@ Events
   Generated for client-side FTP commands.
-   See `Wikipedia <http://en.wikipedia.org/wiki/File_Transfer_Protocol>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/File_Transfer_Protocol>`__ for
   more information about the FTP protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_Gnutella.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_Gnutella.events.bif.zeek.rst
@ -32,7 +32,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Gnutella>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Gnutella>`__ for more
   information about the Gnutella protocol.
   .. zeek:see:: gnutella_establish gnutella_http_notify gnutella_not_establish
@ -50,7 +50,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Gnutella>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Gnutella>`__ for more
   information about the Gnutella protocol.
   .. zeek:see:: gnutella_binary_msg  gnutella_http_notify gnutella_not_establish
@ -68,7 +68,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Gnutella>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Gnutella>`__ for more
   information about the Gnutella protocol.
   .. zeek:see:: gnutella_binary_msg gnutella_establish gnutella_not_establish
@ -86,7 +86,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Gnutella>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Gnutella>`__ for more
   information about the Gnutella protocol.
   .. zeek:see:: gnutella_binary_msg gnutella_establish gnutella_http_notify
@ -104,7 +104,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Gnutella>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Gnutella>`__ for more
   information about the Gnutella protocol.
   .. zeek:see:: gnutella_binary_msg gnutella_establish gnutella_http_notify
@ -122,7 +122,7 @@ Events
   TODO.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Gnutella>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Gnutella>`__ for more
   information about the Gnutella protocol.
   .. zeek:see::  gnutella_binary_msg gnutella_establish gnutella_http_notify
--- a/doc/scripts/base/bif/plugins/Zeek_HTTP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_HTTP.events.bif.zeek.rst
@ -41,7 +41,7 @@ Events
   once. Zeek supports persistent and pipelined HTTP sessions and raises
   corresponding events as it parses client/server dialogues.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -73,7 +73,7 @@ Events
   entities. Zeek raises this event just before it starts parsing each entity's
   content.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -116,7 +116,7 @@ Events
   type as specified by the ``Content-Type`` header. If that header is
   missing, this event is still raised with a default value of ``text/plain``.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -150,7 +150,7 @@ Events
   entities. Zeek raises this event at the point when it has finished parsing an
   entity's content.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -180,7 +180,7 @@ Events
   can be quite expensive for HTTP tranders. At the very least, one should
   impose an upper size limit on how much data is being buffered.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -208,7 +208,7 @@ Events
   Generated for errors found when decoding HTTP requests or replies.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -235,7 +235,7 @@ Events
   sessions and raises corresponding events as it parses client/server
   dialogues.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -273,7 +273,7 @@ Events
   message have been processed (and their corresponding ``http_entity_*`` events
   generated).
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -300,7 +300,7 @@ Events
   dialogues. This event is generated as soon as a reply's initial line has
   been parsed, and before any :zeek:id:`http_header` events are raised.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
@ -329,7 +329,7 @@ Events
   dialogues. This event is generated as soon as a request's initial line has
   been parsed, and before any :zeek:id:`http_header` events are raised.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>`__
   for more information about the HTTP protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_ICMP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_ICMP.events.bif.zeek.rst
@ -43,7 +43,7 @@ Events
   Generated for ICMP *echo reply* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -77,7 +77,7 @@ Events
   Generated for ICMP *echo request* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -114,7 +114,7 @@ Events
   as a fallback for those it doesn't.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/ICMPv6>`__ for more
+   <https://en.wikipedia.org/wiki/ICMPv6>`__ for more
   information about the ICMPv6 protocol.
@ -146,7 +146,7 @@ Events
   Generated for ICMP *neighbor advertisement* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -187,7 +187,7 @@ Events
   Generated for ICMP *neighbor solicitation* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -218,7 +218,7 @@ Events
   Generated for ICMPv6 *packet too big* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/ICMPv6>`__ for more
+   <https://en.wikipedia.org/wiki/ICMPv6>`__ for more
   information about the ICMPv6 protocol.
@ -254,7 +254,7 @@ Events
   Generated for ICMPv6 *parameter problem* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/ICMPv6>`__ for more
+   <https://en.wikipedia.org/wiki/ICMPv6>`__ for more
   information about the ICMPv6 protocol.
@ -290,7 +290,7 @@ Events
   Generated for ICMP *redirect* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -325,7 +325,7 @@ Events
   Generated for ICMP *router advertisement* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -384,7 +384,7 @@ Events
   Generated for ICMP *router solicitation* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -415,7 +415,7 @@ Events
   doesn't.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -462,7 +462,7 @@ Events
   Generated for ICMP *time exceeded* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
@ -498,7 +498,7 @@ Events
   Generated for ICMP *destination unreachable* messages.
   See `Wikipedia
-   <http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
+   <https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol>`__ for more
   information about the ICMP protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_IRC.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_IRC.events.bif.zeek.rst
@ -61,7 +61,7 @@ Events
   Generated for an IRC reply of type *luserchannels*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -87,7 +87,7 @@ Events
   Generated for an IRC reply of type *topic*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -117,7 +117,7 @@ Events
   Generated for IRC messages of type *dcc*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
   See `Wikipedia <https://en.wikipedia.org/wiki/Direct_Client-to-Client>`__ for more
@ -166,7 +166,7 @@ Events
   Generated for IRC messages of type *dcc*. This event is generated for
   DCC SEND acknowledge message.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
   See `Wikipedia <https://en.wikipedia.org/wiki/Direct_Client-to-Client>`__ for more
@ -192,7 +192,7 @@ Events
   Generated for IRC messages of type *error*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -222,7 +222,7 @@ Events
   Generated for an IRC reply of type *globalusers*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -252,7 +252,7 @@ Events
   Generated when a server rejects an IRC nickname.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -276,7 +276,7 @@ Events
   Generated for IRC messages of type *invite*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -310,7 +310,7 @@ Events
   Generated for IRC messages of type *join*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -337,7 +337,7 @@ Events
   Generated for IRC messages of type *kick*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -373,7 +373,7 @@ Events
   Generated for IRC commands forwarded from the server to the client.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -412,7 +412,7 @@ Events
   Generated for IRC messages of type *mode*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -442,7 +442,7 @@ Events
   Generated for an IRC reply of type *namereply*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -474,7 +474,7 @@ Events
   Generated for an IRC reply of type *luserclient*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -507,7 +507,7 @@ Events
   Generated for IRC messages of type *nick*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -537,7 +537,7 @@ Events
   Generated for IRC messages of type *notice*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -570,7 +570,7 @@ Events
   Generated for IRC messages of type *oper*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -599,7 +599,7 @@ Events
   Generated for IRC replies of type *youreoper* and *nooperhost*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -627,7 +627,7 @@ Events
   Generated for IRC messages of type *part*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -660,7 +660,7 @@ Events
   Generated for IRC messages of type *password*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -687,7 +687,7 @@ Events
   Generated for IRC messages of type *privmsg*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -720,7 +720,7 @@ Events
   Generated for IRC messages of type *quit*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -750,7 +750,7 @@ Events
   Generated for all IRC replies. IRC replies are sent in response to a
   request and come with a reply code.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -783,7 +783,7 @@ Events
   Generated for all client-side IRC commands.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -819,7 +819,7 @@ Events
   Generated for an IRC reply of type *luserme*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -852,7 +852,7 @@ Events
   Generated for IRC messages of type *squery*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -885,7 +885,7 @@ Events
   Generated for IRC messages of type *squit*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -931,7 +931,7 @@ Events
   Generated for IRC messages of type *user*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -966,7 +966,7 @@ Events
   Generated for an IRC reply of type *whoreply*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -1017,7 +1017,7 @@ Events
   Generated for IRC messages of type *who*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -1046,7 +1046,7 @@ Events
   Generated for an IRC reply of type *whoischannels*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -1076,7 +1076,7 @@ Events
   Generated for IRC messages of type *whois*. This event is generated for
   messages coming from both the client and the server.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -1105,7 +1105,7 @@ Events
   Generated for an IRC reply of type *whoisoperator*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
@ -1131,7 +1131,7 @@ Events
   Generated for an IRC reply of type *whoisuser*.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Internet_Relay_Chat>`__ for more
   information about the IRC protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_Ident.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_Ident.events.bif.zeek.rst
@ -29,7 +29,7 @@ Events
   Generated for Ident error replies.
-   See `Wikipedia <http://en.wikipedia.org/wiki/ident_protocol>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/ident_protocol>`__ for more
   information about the Ident protocol.
@ -58,7 +58,7 @@ Events
   Generated for Ident replies.
-   See `Wikipedia <http://en.wikipedia.org/wiki/ident_protocol>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/ident_protocol>`__ for more
   information about the Ident protocol.
@ -90,7 +90,7 @@ Events
   Generated for Ident requests.
-   See `Wikipedia <http://en.wikipedia.org/wiki/ident_protocol>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/ident_protocol>`__ for more
   information about the Ident protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_KRB.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_KRB.events.bif.zeek.rst
@ -45,7 +45,7 @@ Events
   that should be part of the first message in an authenticated
   transaction.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -71,7 +71,7 @@ Events
   doesn't have much useful data, but it's provided in case it's important
   to know that this message was sent.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -91,7 +91,7 @@ Events
   encrypted Ticket Granting Ticket (TGT) for that user. The TGT
   can then be used to request further tickets for other services.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -113,7 +113,7 @@ Events
   contains an encrypted Ticket Granting Ticket (TGT) for that user.
   The TGT can then be used to request further tickets for other services.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -133,7 +133,7 @@ Events
   A Kerberos 5 ``Credential Message`` as defined in :rfc:`4120`. This is
   a private (encrypted) message to forward credentials.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -155,7 +155,7 @@ Events
   A Kerberos 5 ``Error Message`` as defined in :rfc:`4120`.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -177,7 +177,7 @@ Events
   have much useful data, but it's provided in case it's important to
   know that this message was sent.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -197,7 +197,7 @@ Events
   A Kerberos 5 ``Safe Message`` as defined in :rfc:`4120`. This is a
   safe (checksummed) application message.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -223,7 +223,7 @@ Events
   authenticate to a Kerberized service, the client requests a Service
   Ticket, which will be returned in the TGS reply.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
@ -245,7 +245,7 @@ Events
   which is encrypted with the service's long-term key, and which the
   client can use to authenticate to that service.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Kerberos_%28protocol%29>`__ for
   more information about the Kerberos protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_Login.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_Login.events.bif.zeek.rst
@ -48,7 +48,7 @@ Events
   protocol includes options for negotiating encryption. When such a series of
   options is successfully negotiated, the event engine generates this event.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
@ -68,7 +68,7 @@ Events
   option is sent from client to server and the server replies that it accepts
   the authentication, then the event engine generates this event.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
@ -99,7 +99,7 @@ Events
   is sent from client to server and the server replies that it did not accept
   the authentication, then the event engine generates this event.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
@ -128,7 +128,7 @@ Events
   Generated for Telnet/Rlogin sessions when a pattern match indicates
   that no authentication is performed.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
@ -156,7 +156,7 @@ Events
   Generated for an ill-formed or unrecognized Telnet option.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
@ -180,7 +180,7 @@ Events
   Generated for a Telnet option that's incorrectly terminated.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
@ -210,7 +210,7 @@ Events
   do, or what it itself offered in terms of options in the past, then the
   engine generates this event.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
@ -404,7 +404,7 @@ Events
   This information is extracted out of environment variables sent as Telnet
   options.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Telnet>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/Telnet>`__ for more information
   about the Telnet protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_MIME.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_MIME.events.bif.zeek.rst
@ -44,7 +44,7 @@ Events
   expensive.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -72,7 +72,7 @@ Events
   text and files, along with corresponding metadata, for transmission.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -101,7 +101,7 @@ Events
   begins parsing a MIME entity extracted from an email protocol.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -124,7 +124,7 @@ Events
   each MIME entity.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -153,7 +153,7 @@ Events
   finished parsing a MIME entity extracted from an email protocol.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -180,7 +180,7 @@ Events
   the latter should be preferred.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -206,7 +206,7 @@ Events
   Generated for errors found when decoding email MIME entities.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -235,7 +235,7 @@ Events
   files, along with corresponding metadata, for transmission.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
@ -267,7 +267,7 @@ Events
   the data. Thus, if possible, this event should be preferred.
   Zeek's MIME analyzer for emails currently supports SMTP and POP3. See
-   `Wikipedia <http://en.wikipedia.org/wiki/MIME>`__ for more information
+   `Wikipedia <https://en.wikipedia.org/wiki/MIME>`__ for more information
   about MIME.
--- a/doc/scripts/base/bif/plugins/Zeek_MySQL.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_MySQL.events.bif.zeek.rst
@ -105,7 +105,7 @@ Events
   Generated for a change user command from a MySQL client.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -123,7 +123,7 @@ Events
   Generated for a command request from a MySQL client.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -144,7 +144,7 @@ Events
   Generated for a MySQL EOF packet.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -162,7 +162,7 @@ Events
   Generated for an unsuccessful MySQL response.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -184,7 +184,7 @@ Events
   Generated for a client handshake response packet, which includes the username the client is attempting
   to connect as.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -202,7 +202,7 @@ Events
   Generated for a successful MySQL response.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -220,7 +220,7 @@ Events
   Generated for each MySQL ResultsetRow response packet.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -238,7 +238,7 @@ Events
   Generated for the initial server handshake packet, which includes the MySQL server version.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
@ -256,7 +256,7 @@ Events
   Generated for a short client handshake response packet with the CLIENT_SSL
   flag set. Usually the client will initiate a TLS handshake afterwards.
-   See the MySQL `documentation <http://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
+   See the MySQL `documentation <https://dev.mysql.com/doc/internals/en/client-server-protocol.html>`__
   for more information about the MySQL protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_NCP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_NCP.events.bif.zeek.rst
@ -28,7 +28,7 @@ Events
   Generated for NCP replies (Netware Core Protocol).
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetWare_Core_Protocol>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetWare_Core_Protocol>`__ for
   more information about the NCP protocol.
@ -63,7 +63,7 @@ Events
   Generated for NCP requests (Netware Core Protocol).
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetWare_Core_Protocol>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetWare_Core_Protocol>`__ for
   more information about the NCP protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_NTP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_NTP.events.bif.zeek.rst
@ -28,7 +28,7 @@ Events
   Generated for all NTP messages. Different from many other of Zeek's events,
   this one is generated for both client-side and server-side messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Network_Time_Protocol>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Network_Time_Protocol>`__ for
   more information about the NTP protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_NetBIOS.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_NetBIOS.events.bif.zeek.rst
@ -36,7 +36,7 @@ Events
   NetBIOS analyzer processes the NetBIOS session service running on TCP port
   139, and (despite its name!) the NetBIOS datagram service on UDP port 138.
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetBIOS>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetBIOS>`__ for more information
   about NetBIOS.  :rfc:`1002` describes
   the packet format for NetBIOS over TCP/IP, which Zeek parses.
@ -53,7 +53,7 @@ Events
      netbios_session_ret_arg_resp decode_netbios_name decode_netbios_name_type
   .. note:: These days, NetBIOS is primarily used as a transport mechanism for
-      `SMB/CIFS <http://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
+      `SMB/CIFS <https://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
      SMB analyzer parses both SMB-over-NetBIOS and SMB-over-TCP on port 445.
   .. todo:: Zeek's current default configuration does not activate the protocol
@ -70,7 +70,7 @@ Events
   processes the NetBIOS session service running on TCP port 139, and (despite
   its name!) the NetBIOS datagram service on UDP port 138.
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetBIOS>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetBIOS>`__ for more information
   about NetBIOS.  :rfc:`1002` describes
   the packet format for NetBIOS over TCP/IP, which Zeek parses.
@ -87,7 +87,7 @@ Events
      netbios_session_ret_arg_resp decode_netbios_name decode_netbios_name_type
   .. note:: These days, NetBIOS is primarily used as a transport mechanism for
-      `SMB/CIFS <http://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
+      `SMB/CIFS <https://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
      SMB analyzer parses both SMB-over-NetBIOS and SMB-over-TCP on port 445.
   .. todo:: Zeek's current default configuration does not activate the protocol
@ -104,7 +104,7 @@ Events
   processes the NetBIOS session service running on TCP port 139, and (despite
   its name!) the NetBIOS datagram service on UDP port 138.
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetBIOS>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetBIOS>`__ for more information
   about NetBIOS.  :rfc:`1002` describes
   the packet format for NetBIOS over TCP/IP, which Zeek parses.
@ -127,7 +127,7 @@ Events
      netbios_session_ret_arg_resp  decode_netbios_name decode_netbios_name_type
   .. note:: These days, NetBIOS is primarily used as a transport mechanism for
-      `SMB/CIFS <http://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
+      `SMB/CIFS <https://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
      SMB analyzer parses both SMB-over-NetBIOS and SMB-over-TCP on port 445.
   .. todo:: Zeek's current default configuration does not activate the protocol
@ -146,7 +146,7 @@ Events
   NetBIOS analyzer processes the NetBIOS session service running on TCP port
   139, and (despite its name!) the NetBIOS datagram service on UDP port 138.
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetBIOS>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetBIOS>`__ for more information
   about NetBIOS.  :rfc:`1002` describes
   the packet format for NetBIOS over TCP/IP, which Zeek parses.
@ -166,7 +166,7 @@ Events
      netbios_session_ret_arg_resp decode_netbios_name decode_netbios_name_type
   .. note:: These days, NetBIOS is primarily used as a transport mechanism for
-      `SMB/CIFS <http://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
+      `SMB/CIFS <https://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
      SMB analyzer parses both SMB-over-NetBIOS and SMB-over-TCP on port 445.
   .. todo:: This is an oddly named event. In fact, it's probably an odd event
@ -186,7 +186,7 @@ Events
   NetBIOS analyzer processes the NetBIOS session service running on TCP port
   139, and (despite its name!) the NetBIOS datagram service on UDP port 138.
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetBIOS>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetBIOS>`__ for more information
   about NetBIOS.  :rfc:`1002` describes
   the packet format for NetBIOS over TCP/IP, which Zeek parses.
@ -203,7 +203,7 @@ Events
      netbios_session_ret_arg_resp decode_netbios_name decode_netbios_name_type
   .. note:: These days, NetBIOS is primarily used as a transport mechanism for
-      `SMB/CIFS <http://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
+      `SMB/CIFS <https://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
      SMB analyzer parses both SMB-over-NetBIOS and SMB-over-TCP on port 445.
   .. todo:: Zeek's current default configuration does not activate the protocol
@ -220,7 +220,7 @@ Events
   analyzer processes the NetBIOS session service running on TCP port 139, and
   (despite its name!) the NetBIOS datagram service on UDP port 138.
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetBIOS>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetBIOS>`__ for more information
   about NetBIOS.  :rfc:`1002` describes
   the packet format for NetBIOS over TCP/IP, which Zeek parses.
@ -237,7 +237,7 @@ Events
      netbios_session_ret_arg_resp decode_netbios_name decode_netbios_name_type
   .. note:: These days, NetBIOS is primarily used as a transport mechanism for
-      `SMB/CIFS <http://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
+      `SMB/CIFS <https://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
      SMB analyzer parses both SMB-over-NetBIOS and SMB-over-TCP on port 445.
   .. todo:: Zeek's current default configuration does not activate the protocol
@ -254,7 +254,7 @@ Events
   analyzer processes the NetBIOS session service running on TCP port 139, and
   (despite its name!) the NetBIOS datagram service on UDP port 138.
-   See `Wikipedia <http://en.wikipedia.org/wiki/NetBIOS>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/NetBIOS>`__ for more information
   about NetBIOS.  :rfc:`1002` describes
   the packet format for NetBIOS over TCP/IP, which Zeek parses.
@ -271,7 +271,7 @@ Events
      netbios_session_request decode_netbios_name decode_netbios_name_type
   .. note:: These days, NetBIOS is primarily used as a transport mechanism for
-      `SMB/CIFS <http://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
+      `SMB/CIFS <https://en.wikipedia.org/wiki/Server_Message_Block>`__. Zeek's
      SMB analyzer parses both SMB-over-NetBIOS and SMB-over-TCP on port 445.
   .. todo:: This is an oddly named event.
--- a/doc/scripts/base/bif/plugins/Zeek_POP3.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_POP3.events.bif.zeek.rst
@ -36,7 +36,7 @@ Events
   mails. This event is generated once for each line that's part of such a
   response.
-   See `Wikipedia <http://en.wikipedia.org/wiki/POP3>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/POP3>`__ for more information
   about the POP3 protocol.
@ -63,7 +63,7 @@ Events
   Generated for unsuccessful authentications on POP3 connections.
-   See `Wikipedia <http://en.wikipedia.org/wiki/POP3>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/POP3>`__ for more information
   about the POP3 protocol.
@ -94,7 +94,7 @@ Events
   Generated for successful authentications on POP3 connections.
-   See `Wikipedia <http://en.wikipedia.org/wiki/POP3>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/POP3>`__ for more information
   about the POP3 protocol.
@ -125,7 +125,7 @@ Events
   Generated for server-side replies to commands on POP3 connections.
-   See `Wikipedia <http://en.wikipedia.org/wiki/POP3>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/POP3>`__ for more information
   about the POP3 protocol.
@ -159,7 +159,7 @@ Events
   Generated for client-side commands on POP3 connections.
-   See `Wikipedia <http://en.wikipedia.org/wiki/POP3>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/POP3>`__ for more information
   about the POP3 protocol.
@ -193,7 +193,7 @@ Events
   generated if that happens and the analyzer then stops processing the
   connection.
-   See `Wikipedia <http://en.wikipedia.org/wiki/POP3>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/POP3>`__ for more information
   about the POP3 protocol.
@ -216,7 +216,7 @@ Events
   finds state transitions that do not conform to the protocol specification,
   or other situations it can't handle, it raises this event.
-   See `Wikipedia <http://en.wikipedia.org/wiki/POP3>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/POP3>`__ for more information
   about the POP3 protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_RADIUS.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_RADIUS.events.bif.zeek.rst
@ -28,7 +28,7 @@ Events
   Generated for each RADIUS attribute.
-   See `Wikipedia <http://en.wikipedia.org/wiki/RADIUS>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/RADIUS>`__ for more
   information about RADIUS.
@ -48,7 +48,7 @@ Events
   Generated for RADIUS messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/RADIUS>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/RADIUS>`__ for more
   information about RADIUS.
--- a/doc/scripts/base/bif/plugins/Zeek_RPC.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_RPC.events.bif.zeek.rst
@ -229,7 +229,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -265,7 +265,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -301,7 +301,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -337,7 +337,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -373,7 +373,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -408,7 +408,7 @@ Events
   analyzer does not implement.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -439,7 +439,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -468,7 +468,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -504,7 +504,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -540,7 +540,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -576,7 +576,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -612,7 +612,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -648,7 +648,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -684,7 +684,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -720,7 +720,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -756,7 +756,7 @@ Events
   reply, or an unanswered request has timed out.
   NFS is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
+   <https://en.wikipedia.org/wiki/Network_File_System_(protocol)>`__ for more
   information about the service.
@ -815,7 +815,7 @@ Events
   Generated for failed Portmapper requests of type *callit*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -847,7 +847,7 @@ Events
   Generated for failed Portmapper requests of type *dump*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -876,7 +876,7 @@ Events
   Generated for failed Portmapper requests of type *getport*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -907,7 +907,7 @@ Events
   Generated for failed Portmapper requests of type *null*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -936,7 +936,7 @@ Events
   Generated for failed Portmapper requests of type *set*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -968,7 +968,7 @@ Events
   Generated for failed Portmapper requests of type *unset*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1003,7 +1003,7 @@ Events
   event is generated.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1031,7 +1031,7 @@ Events
   Generated for Portmapper request/reply dialogues of type *callit*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1062,7 +1062,7 @@ Events
   Generated for Portmapper request/reply dialogues of type *dump*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1090,7 +1090,7 @@ Events
   Generated for Portmapper request/reply dialogues of type *getport*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1120,7 +1120,7 @@ Events
   Generated for Portmapper requests of type *null*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1144,7 +1144,7 @@ Events
   Generated for Portmapper request/reply dialogues of type *set*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1176,7 +1176,7 @@ Events
   Generated for Portmapper request/reply dialogues of type *unset*.
   Portmapper is a service running on top of RPC. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Portmap>`__ for more information about the
+   <https://en.wikipedia.org/wiki/Portmap>`__ for more information about the
   service.
@ -1207,7 +1207,7 @@ Events
   Generated for RPC *call* messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
   about the ONC RPC protocol.
@ -1248,7 +1248,7 @@ Events
   eventually on timeout. In that case, *status* will be set to
   :zeek:enum:`RPC_TIMEOUT`.
-   See `Wikipedia <http://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
   about the ONC RPC protocol.
@ -1292,7 +1292,7 @@ Events
   Generated for RPC *reply* messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/ONC_RPC>`__ for more information
   about the ONC RPC protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_SIP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_SIP.events.bif.zeek.rst
@ -32,7 +32,7 @@ Events
   Generated once for all :abbr:`SIP (Session Initiation Protocol)` headers from the originator or responder.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
   for more information about the :abbr:`SIP (Session Initiation Protocol)` protocol.
@ -55,7 +55,7 @@ Events
   This event is generated as soon as a message's initial line has been parsed.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
   for more information about the :abbr:`SIP (Session Initiation Protocol)` protocol.
@ -73,7 +73,7 @@ Events
   Generated at the end of a :abbr:`SIP (Session Initiation Protocol)` message.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
   for more information about the :abbr:`SIP (Session Initiation Protocol)` protocol.
@ -91,7 +91,7 @@ Events
   Generated for each :abbr:`SIP (Session Initiation Protocol)` header.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
   for more information about the :abbr:`SIP (Session Initiation Protocol)` protocol.
@ -117,7 +117,7 @@ Events
   This event is generated as soon as a reply's initial line has been parsed.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
   for more information about the :abbr:`SIP (Session Initiation Protocol)` protocol.
@ -143,7 +143,7 @@ Events
   This event is generated as soon as a request's initial line has been parsed.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Session_Initiation_Protocol>`__
   for more information about the :abbr:`SIP (Session Initiation Protocol)` protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_SMB.smb1_events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_SMB.smb1_events.bif.zeek.rst
@ -68,7 +68,7 @@ Events
   Generated for all :abbr:`SMB (Server Message Block)`/:abbr:`CIFS (Common Internet File System)` version 1
   messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Server_Message_Block>`__ for more information about the
+   See `Wikipedia <https://en.wikipedia.org/wiki/Server_Message_Block>`__ for more information about the
   :abbr:`SMB (Server Message Block)`/:abbr:`CIFS (Common Internet File System)` protocol. Zeek's
   :abbr:`SMB (Server Message Block)`/:abbr:`CIFS (Common Internet File System)` analyzer parses
   both :abbr:`SMB (Server Message Block)`-over-:abbr:`NetBIOS (Network Basic Input/Output System)` on
--- a/doc/scripts/base/bif/plugins/Zeek_SMB.smb2_events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_SMB.smb2_events.bif.zeek.rst
@ -51,7 +51,7 @@ Events
   Generated for :abbr:`SMB (Server Message Block)`/:abbr:`CIFS (Common Internet File System)`
   version 2 messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Server_Message_Block>`__ for more information about the
+   See `Wikipedia <https://en.wikipedia.org/wiki/Server_Message_Block>`__ for more information about the
   :abbr:`SMB (Server Message Block)`/:abbr:`CIFS (Common Internet File System)` protocol. Zeek's
   :abbr:`SMB (Server Message Block)`/:abbr:`CIFS (Common Internet File System)` analyzer parses
   both :abbr:`SMB (Server Message Block)`-over-:abbr:`NetBIOS (Network Basic Input/Output System)` on
--- a/doc/scripts/base/bif/plugins/Zeek_SMTP.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_SMTP.events.bif.zeek.rst
@ -34,7 +34,7 @@ Events
   corresponding end marker ``.`` is seen. A handler may want to reassemble
   the pieces as they come in if stream-analysis is required.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
   for more information about the SMTP protocol.
@ -63,7 +63,7 @@ Events
   Generated for server-side SMTP commands.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
   for more information about the SMTP protocol.
@ -104,7 +104,7 @@ Events
   Generated for client-side SMTP commands.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
   for more information about the SMTP protocol.
@ -153,7 +153,7 @@ Events
   event that it sees even though it would not expect so at the current point
   of the communication.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
+   See `Wikipedia <https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol>`__
   for more information about the SMTP protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_SSL.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_SSL.events.bif.zeek.rst
@ -74,7 +74,7 @@ Events
   sends an *alert* record, that in turn triggers this event. After an *alert*,
   any endpoint may close the connection immediately.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
   more information about the SSL/TLS protocol.
@ -157,7 +157,7 @@ Events
   of that as it can. This event provides access to the initial information
   sent by the client.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
   more information about the SSL/TLS protocol.
@ -354,7 +354,7 @@ Events
   handshake and its endpoints consider it as fully established. Typically,
   everything from now on will be encrypted.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
   more information about the SSL/TLS protocol.
@ -942,7 +942,7 @@ Events
   of that as it can. This event provides access to the initial information
   sent by the client.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
   more information about the SSL/TLS protocol.
@ -1029,7 +1029,7 @@ Events
   ticket to the client that can later be used for resuming the session. The
   mechanism is described in :rfc:`4507`.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
+   See `Wikipedia <https://en.wikipedia.org/wiki/Transport_Layer_Security>`__ for
   more information about the SSL/TLS protocol.
--- a/doc/scripts/base/bif/plugins/Zeek_X509.events.bif.zeek.rst
+++ b/doc/scripts/base/bif/plugins/Zeek_X509.events.bif.zeek.rst
@ -34,7 +34,7 @@ Events
   Generated for encountered X509 certificates, e.g., in the clear SSL/TLS
   connection handshake.
-   See `Wikipedia <http://en.wikipedia.org/wiki/X.509>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/X.509>`__ for more information
   about the X.509 format.
@ -96,7 +96,7 @@ Events
   Generated for X509 extensions seen in a certificate.
-   See `Wikipedia <http://en.wikipedia.org/wiki/X.509>`__ for more information
+   See `Wikipedia <https://en.wikipedia.org/wiki/X.509>`__ for more information
   about the X.509 format.
--- a/doc/scripts/base/bif/strings.bif.zeek.rst
+++ b/doc/scripts/base/bif/strings.bif.zeek.rst
@ -434,7 +434,7 @@ Functions
   :Type: :zeek:type:`function` (s1: :zeek:type:`string`, s2: :zeek:type:`string`) : :zeek:type:`count`
   Calculates the Levenshtein distance between the two strings. See `Wikipedia
-   <http://en.wikipedia.org/wiki/Levenshtein_distance>`__ for more information.
+   <https://en.wikipedia.org/wiki/Levenshtein_distance>`__ for more information.
   :param s1: The first string.
@ -724,7 +724,7 @@ Functions
   :Type: :zeek:type:`function` (s1: :zeek:type:`string`, s2: :zeek:type:`string`, params: :zeek:type:`sw_params`) : :zeek:type:`sw_substring_vec`
   Uses the Smith-Waterman algorithm to find similar/overlapping substrings.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Smith%E2%80%93Waterman_algorithm>`__.
+   See `Wikipedia <https://en.wikipedia.org/wiki/Smith%E2%80%93Waterman_algorithm>`__.
   :param s1: The first string.
--- a/doc/scripts/base/bif/zeek.bif.zeek.rst
+++ b/doc/scripts/base/bif/zeek.bif.zeek.rst
@ -1327,7 +1327,7 @@ Functions
   :Type: :zeek:type:`function` (data: :zeek:type:`string`) : :zeek:type:`entropy_test_result`
   Performs an entropy test on the given data.
-   See http://www.fourmilab.ch/random.
+   See https://www.fourmilab.ch/random.
   :param data: The data to compute the entropy for.
@ -1854,7 +1854,7 @@ Functions
   See `<https://en.wikipedia.org/wiki/Rendezvous_hashing>`_.
   The weight function used is the one recommended in the original
-   :param paper: `<http://www.eecs.umich.edu/techreports/cse/96/CSE-TR-316-96.pdf>`_.
+   :param paper: `<https://www.eecs.umich.edu/techreports/cse/96/CSE-TR-316-96.pdf>`_.
   :param key_digest: A 32-bit digest of a key.  E.g. use :zeek:see:`fnv1a32` to
@ -4102,7 +4102,7 @@ Functions
   Converts a bytes representation of a UUID into its string form. For example,
   given a string of 16 bytes, it produces an output string in this format:
   ``550e8400-e29b-41d4-a716-446655440000``.
-   See `<http://en.wikipedia.org/wiki/Universally_unique_identifier>`_.
+   See `<https://en.wikipedia.org/wiki/Universally_unique_identifier>`_.
   :param uuid: The 16 bytes of the UUID.
--- a/doc/scripts/base/init-bare.zeek.rst
+++ b/doc/scripts/base/init-bare.zeek.rst
@ -10868,7 +10868,7 @@ Types
   BitTorrent "benc" value. Note that "benc" = Bencode ("Bee-Encode"), per
-   http://en.wikipedia.org/wiki/Bencode.
+   https://en.wikipedia.org/wiki/Bencode.
   .. zeek:see:: bittorrent_benc_dir
@ -12453,7 +12453,7 @@ Types
   Computed entropy values. The record captures a number of measures that are
   computed in parallel. See `A Pseudorandom Number Sequence Test Program
-   <http://www.fourmilab.ch/random>`_ for more information, Zeek uses the same
+   <https://www.fourmilab.ch/random>`_ for more information, Zeek uses the same
   code.
   .. zeek:see:: entropy_test_add entropy_test_finish entropy_test_init find_entropy
--- a/doc/scripts/base/protocols/finger/spicy-events.zeek.rst
+++ b/doc/scripts/base/protocols/finger/spicy-events.zeek.rst
@ -27,7 +27,7 @@ Events
   Generated for Finger replies.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Finger_protocol>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Finger_protocol>`__ for more
   information about the Finger protocol.
@ -45,7 +45,7 @@ Events
   Generated for Finger requests.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Finger_protocol>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Finger_protocol>`__ for more
   information about the Finger protocol.
--- a/doc/scripts/base/protocols/syslog/spicy-events.zeek.rst
+++ b/doc/scripts/base/protocols/syslog/spicy-events.zeek.rst
@ -26,7 +26,7 @@ Events
   Generated for monitored Syslog messages.
-   See `Wikipedia <http://en.wikipedia.org/wiki/Syslog>`__ for more
+   See `Wikipedia <https://en.wikipedia.org/wiki/Syslog>`__ for more
   information about the Syslog protocol.
--- a/doc/scripts/policy/protocols/ssl/heartbleed.zeek.rst
+++ b/doc/scripts/policy/protocols/ssl/heartbleed.zeek.rst
@ -4,7 +4,7 @@ policy/protocols/ssl/heartbleed.zeek
 ====================================
 .. zeek:namespace:: Heartbleed
-Detect the TLS heartbleed attack. See http://heartbleed.com for more.
+Detect the TLS heartbleed attack. See https://heartbleed.com for more.
 :Namespace: Heartbleed
 :Imports: :doc:`base/frameworks/notice </scripts/base/frameworks/notice/index>`, :doc:`base/protocols/ssl </scripts/base/protocols/ssl/index>`
--- a/doc/scripts/zeekygen/example.zeek.rst
+++ b/doc/scripts/zeekygen/example.zeek.rst
@ -11,7 +11,7 @@ version.
 Comments in the from ``##!`` are meant to summarize the script's
 purpose.  They are transferred directly into the generated
-`reStructuredText <http://docutils.sourceforge.net/rst.html>`_
+`reStructuredText <https://docutils.sourceforge.net/rst.html>`_
 (reST) document associated with the script.
 .. tip:: You can embed directives and roles within ``##``-stylized comments.
--- a/doc/scripts/zeekygen/index.rst
+++ b/doc/scripts/zeekygen/index.rst
@ -20,7 +20,7 @@ extra scripts needed or used by the documentation process.
   Comments in the from ``##!`` are meant to summarize the script's
   purpose.  They are transferred directly into the generated
-   `reStructuredText <http://docutils.sourceforge.net/rst.html>`_
+   `reStructuredText <https://docutils.sourceforge.net/rst.html>`_
   (reST) document associated with the script.
   .. tip:: You can embed directives and roles within ``##``-stylized comments.