From 52a87e506d4fc70bd5922b07a532852d28f28ab6 Mon Sep 17 00:00:00 2001
From: Mehdi Bounya <mehdi.bounya@gmail.com>
Date: Thu, 17 May 2018 23:41:30 +0000
Subject: http:// to https://

---
 user_guide_src/source/libraries/sessions.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to 'user_guide_src/source/libraries/sessions.rst')

diff --git a/user_guide_src/source/libraries/sessions.rst b/user_guide_src/source/libraries/sessions.rst
index 994dc2e08..f2236c633 100644
--- a/user_guide_src/source/libraries/sessions.rst
+++ b/user_guide_src/source/libraries/sessions.rst
@@ -112,7 +112,7 @@ Session data is simply an array associated with a particular session ID
 (cookie).
 
 If you've used sessions in PHP before, you should be familiar with PHP's
-`$_SESSION superglobal <http://php.net/manual/en/reserved.variables.session.php>`_
+`$_SESSION superglobal <https://secure.php.net/manual/en/reserved.variables.session.php>`_
 (if not, please read the content on that link).
 
 CodeIgniter gives access to its session data through the same means, as it
@@ -391,7 +391,7 @@ Destroying a Session
 ====================
 
 To clear the current session (for example, during a logout), you may
-simply use either PHP's `session_destroy() <http://php.net/session_destroy>`_
+simply use either PHP's `session_destroy() <https://secure.php.net/session_destroy>`_
 function, or the ``sess_destroy()`` method. Both will work in exactly the
 same way::
 
@@ -516,7 +516,7 @@ mind that it is in fact not the same code and it has some limitations
 
 To be more specific, it doesn't support PHP's `directory level and mode
 formats used in session.save_path
-<http://php.net/manual/en/session.configuration.php#ini.session.save-path>`_,
+<https://secure.php.net/manual/en/session.configuration.php#ini.session.save-path>`_,
 and it has most of the options hard-coded for safety. Instead, only
 absolute paths are supported for ``$config['sess_save_path']``.
 
@@ -554,7 +554,7 @@ increase - which is the time when it matters - the file system will
 consistently outperform almost all relational database setups.
 
 In addition, if performance is your only concern, you may want to look
-into using `tmpfs <http://eddmann.com/posts/storing-php-sessions-file-caches-in-memory-using-tmpfs/>`_,
+into using `tmpfs <https://eddmann.com/posts/storing-php-sessions-file-caches-in-memory-using-tmpfs/>`_,
 (warning: external resource), which can make your sessions blazing fast.
 
 Database Driver
@@ -679,7 +679,7 @@ Memcached Driver
 
 The 'memcached' driver is very similar to the 'redis' one in all of its
 properties, except perhaps for availability, because PHP's `Memcached
-<http://php.net/memcached>`_ extension is distributed via PECL and some
+<https://secure.php.net/memcached>`_ extension is distributed via PECL and some
 Linux distrubutions make it available as an easy to install package.
 
 Other than that, and without any intentional bias towards Redis, there's
@@ -754,7 +754,7 @@ when creating a session driver for CodeIgniter:
 
 
   - Implement the `SessionHandlerInterface
-    <http://php.net/sessionhandlerinterface>`_ interface.
+    <https://secure.php.net/sessionhandlerinterface>`_ interface.
 
     .. note:: You may notice that ``SessionHandlerInterface`` is provided
         by PHP since version 5.4.0. CodeIgniter will automatically declare
@@ -1016,7 +1016,7 @@ Class Reference
 
 		.. note:: This method is just an alias for PHP's native
 			`session_regenerate_id()
-			<http://php.net/session_regenerate_id>`_ function.
+			<https://secure.php.net/session_regenerate_id>`_ function.
 
 	.. php:method:: sess_destroy()
 
@@ -1030,7 +1030,7 @@ Class Reference
 
 		.. note:: This method is just an alias for PHP's native
 			`session_destroy()
-			<http://php.net/session_destroy>`_ function.
+			<https://secure.php.net/session_destroy>`_ function.
 
 	.. php:method:: __get($key)
 
-- 
cgit v1.2.3-24-g4f1b