Re:Forcing Wordpress sites to use https even when not directed
by k8tte on Thursday July 23, 2015 @08:01AM
(#9935149)
Agree. I'm having a hard time to see how this is Chrome's fault. All discussion i've seen indicate that wordpress and woocommerce treat the HTTPS header in special (and non-standard) ways
[ Parent
| on HN ]
Re:Forcing Wordpress sites to use https even when not directed
by martius on Thursday July 23, 2015 @08:28AM
(#9935232)
It's Chrome fault to use push for a new standardized header without properly checking its impact: the issue has been raised during the beta phase, but they underestimated it and did not rollback.
I believe it is known that some old reverse-proxies used this header before a standard solution emerged (X-forwarded-proto), Wordpress probably had to deal with this surprising behavior at some point.
Also, by naming a header "HTTPS", one could expect collision with a non-standard behavior: this is very common with HTTP/1.1.
Re:Forcing Wordpress sites to use https even when not directed
by k8tte on Thursday July 23, 2015 @09:22AM
(#9935501)
I agree. However, non-standard conforming software should continue to use the X- prefix, like if these proxies used a "X-HTTPS" indicating it is a non-standard header, this would be a non-issue.