Title: Callback problems when using HTTPS
Last modified: August 22, 2016

---

# Callback problems when using HTTPS

 *  Resolved [edlund](https://wordpress.org/support/users/edlund/)
 * (@edlund)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/callback-problems-when-using-https/)
 * Hi there
 * I am running a woocommerce site purely on https. However the callback url in 
   woocommerce quickpay is forced to be http. Due to the server setup this means
   that the callbacks fail.
 * Is there a specific reason not to use https for callbacks? And if not is it possible
   that it can be changed to use the site default?
 * /Kristian
 * [https://wordpress.org/plugins/woocommerce-quickpay/](https://wordpress.org/plugins/woocommerce-quickpay/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [PerfectSolution](https://wordpress.org/support/users/perfectsolution/)
 * (@perfectsolution)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/callback-problems-when-using-https/#post-5449020)
 * Hi Kristian,
 * Thank you for your post.
 * I have followed the callback example mentioned in WooCommerce’s official payment
   gateway docs which can be found on [http://docs.woothemes.com/document/payment-gateway-api/](http://docs.woothemes.com/document/payment-gateway-api/)
 * I must admit that I am not entirely sure why you would always replace https with
   http. I suppose there is a good reason to this, but as of right now, I cannot
   give you the very specific reason.
 * Since this is a big problem with your current setup, I suggest you modify classes/
   woocommerce-quickpay-order.php.
 * Replace:
 *     ```
       public function get_callback_url() {
        return str_replace( 'https:', 'http:', add_query_arg( 'wc-api', 'WC_Quickpay', home_url( '/' ) ) );
       }
       ```
   
 * With;
 *     ```
       public function get_callback_url() {
        return add_query_arg( 'wc-api', 'WC_Quickpay', home_url( '/' ) );
       }
       ```
   
 * Please be aware that these changes will be lost in case of a plugin update.
 *  Thread Starter [edlund](https://wordpress.org/support/users/edlund/)
 * (@edlund)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/callback-problems-when-using-https/#post-5449087)
 * I understand your concern, however I don’t understand why either.
 * I have done something like that already, but I am not too keen on that solution
   since it is for a customer. And I really want her to be able to update the plugin.
 * Would it be possible to add a filter to the callback url? If that would be an
   okay solution I am willing to submit it as a pull request. If that makes it easier
   for you.
 *  Plugin Author [PerfectSolution](https://wordpress.org/support/users/perfectsolution/)
 * (@perfectsolution)
 * [11 years ago](https://wordpress.org/support/topic/callback-problems-when-using-https/#post-5449241)
 * To your information this problem is solved in 3.0.7.
 *  Thread Starter [edlund](https://wordpress.org/support/users/edlund/)
 * (@edlund)
 * [11 years ago](https://wordpress.org/support/topic/callback-problems-when-using-https/#post-5449242)
 * Thanks 🙂

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Callback problems when using HTTPS’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/woocommerce-quickpay_263a40.svg)
 * [Quickpay for WooCommerce](https://wordpress.org/plugins/woocommerce-quickpay/)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce-quickpay/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce-quickpay/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-quickpay/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce-quickpay/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [edlund](https://wordpress.org/support/users/edlund/)
 * Last activity: [11 years ago](https://wordpress.org/support/topic/callback-problems-when-using-https/#post-5449242)
 * Status: resolved