6 files changed, 10 insertions, 10 deletions
diff --git a/Bugzilla/Constants.pm b/Bugzilla/Constants.pm
index 9c8f39b4a..37917d305 100644
--- a/Bugzilla/Constants.pm
+++ b/Bugzilla/Constants.pm
@@ -213,7 +213,7 @@ sub BUGZILLA_VERSION {
 
 # A base link to the current REST Documentation. We place it here
 # as it will need to be updated to whatever the current release is.
-use constant REST_DOC => "http://www.bugzilla.org/docs/tip/en/html/api/";
+use constant REST_DOC => "https://bugzilla.readthedocs.io/en/latest/api/";
 
 # Location of the remote and local XML files to track new releases.
 use constant REMOTE_FILE => 'http://updates.bugzilla.org/bugzilla-update.xml';
diff --git a/Bugzilla/DB/Schema.pm b/Bugzilla/DB/Schema.pm
index 7448d8878..0464466af 100644
--- a/Bugzilla/DB/Schema.pm
+++ b/Bugzilla/DB/Schema.pm
@@ -79,7 +79,7 @@ Bugzilla::DB.
 
 If this is your first time looking at Schema.pm, especially if
 you are making changes to the database, please take a look at
-L<http://www.bugzilla.org/docs/developer.html#sql-schema> to learn
+L<https://www.bugzilla.org/docs/developer.html#sql-schema> to learn
 more about how this integrates into the rest of Bugzilla.
 
 =cut
@@ -3179,6 +3179,6 @@ database-specific basis:
 
 L<Bugzilla::DB>
 
-L<http://www.bugzilla.org/docs/developer.html#sql-schema>
+L<https://www.bugzilla.org/docs/developer.html#sql-schema>
 
 =cut
diff --git a/Bugzilla/Extension.pm b/Bugzilla/Extension.pm
index 7e53d87f3..baf2286e1 100644
--- a/Bugzilla/Extension.pm
+++ b/Bugzilla/Extension.pm
@@ -325,7 +325,7 @@ L<Bugzilla/input_params>.
 
 If you need a new hook for your extension and you want that hook to be
 added to Bugzilla itself, see our development process at
-L<http://wiki.mozilla.org/Bugzilla:Developers>.
+L<https://wiki.mozilla.org/Bugzilla:Developers>.
 
 In order for a new hook to be accepted into Bugzilla, it has to work,
 it must have documentation in L<Bugzilla::Hook>, and it must have example
@@ -618,7 +618,7 @@ return C<0> or some false value.
 If you've made an extension and you want to publish it, the first
 thing you'll want to do is package up your extension's code and
 then put a link to it in the appropriate section of
-L<http://wiki.mozilla.org/Bugzilla:Addons>.
+L<https://wiki.mozilla.org/Bugzilla:Addons>.
 
 =head2 Distributing on CPAN
 
@@ -628,7 +628,7 @@ distribute your Bugzilla Extension through CPAN.
 
 The details of making a standard CPAN module are too much to
 go into here, but a lot of it is covered in L<perlmodlib>
-and on L<http://www.cpan.org/> among other places.
+and on L<https://www.cpan.org/> among other places.
 
 When you distribute your extension via CPAN, your F<Extension.pm>
 should simply install itself as F<Bugzilla/Extension/Foo.pm>,
@@ -659,7 +659,7 @@ uses extensions.
 
 If you are an extension author and you'd like some assistance from other
 extension authors or the Bugzilla development team, you can use the
-normal support channels described at L<http://www.bugzilla.org/support/>.
+normal support channels described at L<https://www.bugzilla.org/support/>.
 
 =head1 ADDITIONAL CONSTANTS
 
diff --git a/Bugzilla/Template/Plugin/Hook.pm b/Bugzilla/Template/Plugin/Hook.pm
index 981a1ab53..a2b76a80f 100644
--- a/Bugzilla/Template/Plugin/Hook.pm
+++ b/Bugzilla/Template/Plugin/Hook.pm
@@ -149,4 +149,4 @@ Output from processing template extension.
 
 L<Template::Plugin>
 
-L<http://wiki.mozilla.org/Bugzilla:Writing_Extensions>
+L<https://bugzilla.readthedocs.io/en/latest/integrating/extensions.html>
diff --git a/Bugzilla/WebService/Server/JSONRPC.pm b/Bugzilla/WebService/Server/JSONRPC.pm
index 0fb8b4299..0bd7b4648 100644
--- a/Bugzilla/WebService/Server/JSONRPC.pm
+++ b/Bugzilla/WebService/Server/JSONRPC.pm
@@ -527,7 +527,7 @@ JSON-RPC response.
 When calling the JSON-RPC WebService over GET, you can use the "JSONP"
 method of doing cross-domain requests, if you want to access the WebService
 directly on a web page from another site. JSONP is described at
-L<http://bob.pythonmac.org/archives/2005/12/05/remote-json-jsonp/>.
+L<https://bob.ippoli.to/archives/2005/12/05/remote-json-jsonp/>.
 
 To use JSONP with Bugzilla's JSON-RPC WebService, simply specify a
 C<callback> parameter to jsonrpc.cgi when using it via GET as described above.
diff --git a/Bugzilla/WebService/Server/XMLRPC.pm b/Bugzilla/WebService/Server/XMLRPC.pm
index f5a31b30e..fce865e88 100644
--- a/Bugzilla/WebService/Server/XMLRPC.pm
+++ b/Bugzilla/WebService/Server/XMLRPC.pm
@@ -422,7 +422,7 @@ returned>.
 
 nil is implemented by XMLRPC::Lite, in XMLRPC::Deserializer::decode_value
 in the CPAN SVN since 14th Dec 2008
-L<http://rt.cpan.org/Public/Bug/Display.html?id=20569> and in Fedora's
+L<https://rt.cpan.org/Public/Bug/Display.html?id=20569> and in Fedora's
 perl-SOAP-Lite package in versions 0.68-1 and above.
 
 =end private