Serving HTTP version of site to those who don't support HTTP2 -
i'd move client's site entirely https in order allow http2 work, wondering ok (in eyes of search engines) serve older traffic (of there lot , otherwise suffer perf hit) not support http2?
is dangerous seo point of view? and
could detection tools wurfl?
i want stay current , offer improved perf/security on newer browsers don't want on older browsers in developing countries suffer.
for worth, did tests few weeks ago , got impression google's spiders don't see http/2 yet. @sbordet pointed out upgrade http/2 optional, sure have site responds http/1.1. here few thoughts more:
- google's algorithms penalize slower sites, unlikely take big performance hit using https in servers.
- using https can boost seo. doesn't have http/2.
- popular browsers don't support http/2: safari , ie. safari doesn't support tls crypto-suite compatible http/2, afaik. won't cause problems long list http/2-compatible suites first in tls server hello: ecdhe-rsa-aes128-gcm-sha256 , ecdhe-rsa-aes256-gcm-sha384 ones know of. can list weaker suites.
Comments
Post a Comment