I am working to increase security and speed on a LAMP server. After enabling mod_http2 in the server, in order to increase website and the SuiteCRM speed, I noticed SuiteCRM performs the opposite and load slower. It will now and then display the error message “browser error…javascript” or whatever. This may be due to the fact that HTTP/2 compresses css, js and other files.
The fact is that HTTP/2 is fast becoming the standard for companies as it compresses files, reduces bandwidth usage, reduces costs and speeds up website and software loading. W3Techs statistics show that HTTP/2 is being used by 16% of websites, globaly and by the graphic you can see here https://w3techs.com/technologies/details/ce-http2/all/all HTTP/2 usage is increasing fast.
The question is not “if” but “when” SuiteCRM will need to be compatible with HTTP/2 in order to keep market share/sales, etc.
I wonder if we could add “Compatibility with HTTP/2” to the wish list for SuiteCRM developers.
HTTP/2 compresses files, but it also uncompresses them at the destination… it really shouldn’t make a difference.
So, if you find you are having problems with HTTP/2, the best thing would be to get down to a reproducible error and file it on GitHub. If there are some things that don’t play well with HTTP/2, they can be fixed individually.
I don’t know much about this, but from what I hear the job of migrating to HTTP/2 is mostly done when you’ve migrated your site to HTTPS successfully. But I don’t think SuiteCRM is easy or ready to migrate to HTTPS. So you could start by that part…
pgr thank you. That was exactly the case. I migrated SuiteCRM to HTTPS. It is a test install and I found no incompatibilities with HTTPS. I am moving it now to production and if my tests are confirmed I expect zero issues with SuiteCRM and HTTPS.