php - Wordpress (WooCommerce?) forces https (when it shouldn't) -
i'm experiencing strange issue on woocommerce installation company has taken over. it's not built , unfortunately it's pretty crappy built i'm not sure what's going on in there.
it started "force" https connections, far know nothing has changed in nether code nor admin. running git on server , nothing has changed in working tree, , searched uploads folder suspicious files no results. it's unlikely kind of malware. site not set https/ssl of course trigger timeout.
i checked database , both home_url
, site_url
set "http://...". woocommerce option "force ssl" set false. running plugin "better wp security/ithemes security" offers "force ssl"-option 1 set false too.
i tried setting both constants force_ssl_admin
, force_ssl_login
false in wp-config.php - still no luck. tried using .htaccess rewrite rules didn't either.
it seems connected request header; https: 1
(tested $ curl -i -h"https: 1" http://...
). when 1 set 0
not happen. chrome seems send default, not case other browsers. tried clearing cookies/data etc. problem appears in colleague's browser (and has never visited site before). hosting company says not related server configuration.
has experienced before, or know related to?
update: running curl -i -h"https: 1" http://www.example.com/wp-admin/
pretty confirms has wordpress. cookies set wpml indicates wordpress initialized. check location:
header:
http/1.1 302 moved temporarily server: apache x-powered-by: php/5.6.11 expires: wed, 11 jan 1984 05:00:00 gmt cache-control: no-cache, must-revalidate, max-age=0 pragma: no-cache set-cookie: _icl_current_admin_language=sv; expires=wed, 22-jul-2015 16:06:25 gmt; max-age=7200; path=/wp-admin/ set-cookie: _icl_current_language=sv; expires=thu, 23-jul-2015 14:06:25 gmt; max-age=86400; path=/ set-cookie: phpsessid=xxx; path=/ location: https://www.example.com/wp-login.php?redirect_to=https%3a%2f%2fwww.example.com%2fwp-admin%2f&reauth=1 vary: accept-encoding content-type: text/html; charset=utf-8 date: wed, 22 jul 2015 14:06:26 gmt x-varnish: nnn age: 0 via: 1.1 varnish connection: keep-alive
updating woocommerce 2.3.13 fixed me
Comments
Post a Comment