How to override core is_ssl() function?

4 Views

I am looking to override a function in functions.php through a theme or plugin. Specifically, is_ssl(), which does not have any filter or action hooks. Obviously, the easy why would be to update functions.php itself, but this will leave issues with upgrade and compatibility. How could this be done.

Edit:
The goal is to overwrite is_ssl() function to return true when specific flag is set in the request header.

Read More

Is it possible with the override-function?

Post Views: 4

Related posts

Leave a Reply

4 comments

  1. If you look at the source of the is_ssl() function you’ll see it checks various $_SERVER variables. Therefore, you could try adding this to a plugin:

    if ( isset( $_SERVER['HTTP_MY_CUSTOM_HEADER'] ) )
  $_SERVER['HTTPS'] = 'on';

    You’d need to call that code as early as possible, ie. directly in the plugin body rather than on a hook.

  2. You cannot override a function once it is defined. That is pure PHP. Some functions are wrapped in a conditional that lets you cheat around this– look at pluggable.php. Otherwise, you just can’t do it. You’ll get a fatal error.

    Your best bet to solve this is probably a child theme but without a lot of details I couldn’t say how to go about it, and even so success depends on how cooperative your ‘parent’ theme is. It may be written inis uch a way as to make this very hard on you.

  3. There is no easy way to do this…or at least no mass-adopted way anymore. Namespace wont really work here and every update will erase a hard edit unless its in a config (messy way to do it). vQmod is an angle, but never tried it with WordPress.

    Plugins are executed before that function, so if its proxy/balancer/SSL support you need then you can spoof the $_SERVER['HTTPS'] to be 'on'. An array merge might work good here for this if you are dealing with multiple header triggers.

    Keep in mind, if you are making this a plugin, prefix your folder and script(s) so they sort at the top of the file list. Example is something like -my-router.php found in -my-router folder. The dash will sort plugin to top which should render first in chain. This is needed in case other plugins call is_ssl() or something like wp_enqueue_style() before your your plugin mitigates it.

  4. After considerable research, I believe that there is no good answer to this.

    The best answer would be to modify $_SERVER early on, but not every environment allows you to do this. Unfortunately, a direct hack is the only way to do this.

    This is necessary behind load balancers that obfuscate ssl origin. Implementing WordPress in Azure using Active Directory Authentication (which forces ssl, but sends all results to port 80, non-ssl), my solution was to modify is_ssl to always return true.