Deprecated: Joomla\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 41

Deprecated: Return type of Joomla\Input\Input::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 170

Deprecated: Joomla\CMS\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Input.php on line 31

Deprecated: Joomla\CMS\Input\Cookie implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Cookie.php on line 21

Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Uri/Uri.php on line 141
Problem accessing some sites and HTTPS Everywhere. - Macrotone Blogs

Macrotone Blogs

Macrotone blogs upon Joomla, our products and other matters.
Font size: +
1 minute reading time (172 words)

Problem accessing some sites and HTTPS Everywhere.


We have noticed a small problem recently when trying to access a specific site ‘www.joomla.org’.  Not a particularly unusual place to access given some of our work. What was confusing was that other sites in the same domain were all accessible.

After much head scratching and trial and error, clearing cache’s and disabling cookies etc.  we eventually discovered the cause.

We use an extension names HTTPS Everywhere in our Chrome and Firefox browsers and it was this that was forcing the use of the HTTPS protocol on the site.  The result was that the site was always timing out.  Once identified the resolution was (as usual) simple, and involved disabling the use of HTTPS for that specific address.  Once this was done the problem was solved.

This type of problem may of course impact other web addresses, but after six months of use we must admit it is the only site that has every given us any problem. One for others to note in case they have the same type of problem.

×
Stay Informed

When you subscribe to the blog, we will send you an e-mail when there are new updates on the site so you wouldn't miss them.

Web Standards
SPAM and IP blocking
 
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries