Incompatible with HTTP/2?

I’m having the same problem with the infinite loop spinner, but don’t know if my host has upgraded my server. I haven’t changed anything, it suddenly stopped working.

On Firefox, use this addon to show a blue lightning bolt indicator for sites that are fully HTTP/2, like this forum or Google:

https://addons.mozilla.org/en-US/firefox/addon/spdy-indicator/

On Chrome:

https://chrome.google.com/webstore/detail/http2-and-spdy-indicator/mpbpobfflnpcgagjijhmgnchggcjblin?hl=en

Really it doesn’t work with HTTP/2? I’ve been thinking about using this plugin. ?? sad news.

I know. I have to find another lazy load option. I’m using ngx_pagespeed but I find its lazy load doesn’t work well either.

Just upgraded to 1.5.0 and everything seems to be working fine with HTTP/2, which is great news.

Hello jshare

Thank you for updating your thread and marking the topic as resolved. Good to hear that the Fix in the upgrade resolved the issue for you.

Regards
Steve

The update to 1.5.1 reintroduced the issue in IE and Edge, so I’m rolling back to 1.5.0. Chrome and Firefox are fine though.

Hello jshare

OK we are trying to get our head fully around http/2 – It seems to be early days with the protocol only being released in May this year.

According to Wikipedia only 2.3% of the top 10 million websites in the world currently support http/2

It also seem to be limited by a number of factors – not least

Only these modern browsers support it and only via SSL connection – only 1/4 of the web

HTTP/2 capable browser Global Market Share
IE 11 on Windows 10 0.14%
Edge 12, and 13 0.35%
Firefox 36 – 45 5.09%
Chrome 41 – 49 15.06%
Safari 9 0.91%
Opera 28 – 34 0.57%
Safari for iOS 9.1 1.07%
Opera 30 for Android 0.01%
Chrome 46 for Android 3.59%
Firefox 41 for Android 0.01%
Total 26.79%

I see you mention your test in IE – please note that http/2 is only supported on widows 10

Seems also that only certain servers support http/2

You mentioned nginx – seem only version 1.9.5 have support – Apache support starts at version 2.4.12 with the module mod_http2 installed and appropriate patches must be applied to the source code of the server in order for it to support that module. – From version 2.4.17 don’t need the supporting patches.

Despite that it seems that the increase in speed is promised to be a whopping 30% over the http/1 protocol. BUT many things in developers code also have to change – there is a good post about that here on the Cloudflare site

Couple http/2 with PHP 7 (only released 12 days ago and have very limited support and no backward compat) which promised to double the speed of of PHP 5.6, Depreciation of SHA-1 replaced by SHA-2, WordPress 4.4 srcset attribute responsive images and soon full support for WP Rest API (infrastructure added to core in 4.4)

It is all moving so quickly – maintaining 92 plugins (of which 19 are free on www.ads-software.com) it gets hectic trying to keep up with it all – especially in the early days of a new protocol release when backward compatibility has to be maintained.

I mean it is difficult to tweak the plugin to support new and not yet universally used protocols if that tweak breaks the plugin in older protocols still used by the majority of people if there is not way to add backward compatibility.

Just some thoughts

Regards
Steve

I’m on Win10, latest IE.

Thanks for the explanation, but you don’t really need to justify all that.

Honestly, you need to have priorities, and I agree with you that making the plugin http2 compliant probably shouldn’t be at the top of the list, or even near it (for now; compliance is only going to grow). But you should still want people to report bugs, and a best practice is to spend 15 minutes doing a quick investigation of any new bug reports because the solution is often obvious, and you can then decide whether to just bang it out quickly (if possible) or tell bug reporters it’s going to have to wait ??

Meanwhile, I’ll stay on 1.5.0 but keep checking whenever you update, or until I find a better plugin that is compliant (although it’s not a priority for me to actively look right now).