From f8278e53572d1b23d4d92e2b54ac67e896bfb14d Mon Sep 17 00:00:00 2001
From: Josh Lockhart <josh@newmediacampaigns.com>
Date: Tue, 19 Jun 2018 14:36:52 -0400
Subject: [PATCH] Update links in Errors section to use https

---
 _posts/09-02-01-Errors.md     | 26 +++++++++++++-------------
 _posts/09-03-01-Exceptions.md |  6 +++---
 2 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/_posts/09-02-01-Errors.md b/_posts/09-02-01-Errors.md
index c510a70..dd38fd9 100644
--- a/_posts/09-02-01-Errors.md
+++ b/_posts/09-02-01-Errors.md
@@ -1,5 +1,5 @@
---- 
-isChild: true 
+---
+isChild: true
 anchor:  errors
 ---
 
@@ -104,7 +104,7 @@ with the following.
 xdebug.scream = On
 {% endhighlight %}
 
-You can also set this value at runtime with the `ini_set` function 
+You can also set this value at runtime with the `ini_set` function
 
 {% highlight php %}
 <?php
@@ -131,8 +131,8 @@ PHP is perfectly capable of being an "exception-heavy" programming language, and
 make the switch. Basically you can throw your "errors" as "exceptions" using the `ErrorException` class, which extends
 the `Exception` class.
 
-This is a common practice implemented by a large number of modern frameworks such as Symfony and Laravel. In debug 
-mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*. 
+This is a common practice implemented by a large number of modern frameworks such as Symfony and Laravel. In debug
+mode *(or dev mode)* both of these frameworks will display a nice and clean *stack trace*.
 
 There are also some packages available for better error and exception handling and reporting. Like [Whoops!], which comes with the default installation of Laravel and can be used in any framework as well.
 
@@ -150,11 +150,11 @@ More information on this and details on how to use `ErrorException` with error h
 
 
 [errorreport]: /#error_reporting
-[Xdebug]: http://xdebug.org/docs/basic
-[Scream]: http://php.net/book.scream
-[Error Control Operators]: http://php.net/language.operators.errorcontrol
-[SitePoint]: http://www.sitepoint.com/
-[Whoops!]: http://filp.github.io/whoops/
-[errorexception]: http://php.net/class.errorexception
-[Predefined Constants for Error Handling]: http://php.net/errorfunc.constants
-[error_reporting]: http://php.net/function.error-reporting
+[Xdebug]: https://xdebug.org/docs/basic
+[Scream]: https://secure.php.net/book.scream
+[Error Control Operators]: https://secure.php.net/language.operators.errorcontrol
+[SitePoint]: https://www.sitepoint.com/
+[Whoops!]: https://filp.github.io/whoops/
+[errorexception]: https://secure.php.net/class.errorexception
+[Predefined Constants for Error Handling]: https://secure.php.net/errorfunc.constants
+[error_reporting]: https://secure.php.net/function.error-reporting
diff --git a/_posts/09-03-01-Exceptions.md b/_posts/09-03-01-Exceptions.md
index 252351f..95c39ab 100644
--- a/_posts/09-03-01-Exceptions.md
+++ b/_posts/09-03-01-Exceptions.md
@@ -71,7 +71,7 @@ standard Exception which is vague, or creating a custom Exception just for that,
 
 
 [splext]: /#standard_php_library
-[exceptions]: http://php.net/language.exceptions
-[splexe]: http://php.net/spl.exceptions
-[nesting-exceptions-in-php]: http://www.brandonsavage.net/exceptional-php-nesting-exceptions-in-php/
+[exceptions]: https://secure.php.net/language.exceptions
+[splexe]: https://secure.php.net/spl.exceptions
+[nesting-exceptions-in-php]: https://www.brandonsavage.net/exceptional-php-nesting-exceptions-in-php/
 [exception-best-practices53]: http://ralphschindler.com/2010/09/15/exception-best-practices-in-php-5-3