Task #2443
closedSupport HTTP/2 protocol for all TDF backends
0%
Description
Currently (2017-12-31) only few backends support HTTP/2 protocol on TDF infrastructure:
https://tinderbox.libreoffice.org
https://opengrok.libreoffice.org
https://api.libreoffice.org
https://dev-builds.libreoffice.org
Note, that the link from devcentral to dev-builds.libreoffice.org is wrong:
http://dev-builds.libreoffice.org/cppcheck_reports/master not https
All other TDF backends don't support HTTP/2:
https://devcentral.libreoffice.org
https://wiki.documentfoundation.org
https://ci.libreoffice.org
https://bugs.documentfoundation.org
https://help.libreoffice.org
https://translations.documentfoundation.org
https://perf.libreoffice.org
https://lcov.libreoffice.org
https://crashreport.libreoffice.org
https://gerrit.libreoffice.org
https://ask.libreoffice.org (there is no link from devcentral for ask)
FWIW: on nginx, these lines would enable HTTP/2 protocoll:
[...]
listen 443 ssl http2;
listen [::]:443 ssl http2;
[...]
Related issues
Updated by Florian Effenberger over 6 years ago
- Is duplicate of Task #2321: Bug 109300 - Please support HTTP/2 added
Updated by Guilhem Moulin over 6 years ago
- Priority changed from Normal to Low
David Ostrovsky wrote:
Note, that the link from devcentral to dev-builds.libreoffice.org is wrong:
http://dev-builds.libreoffice.org/cppcheck_reports/master not https
Wasn't the only http:// link, but others (such as http://help.libreoffice.org have a 301 redirection to https://). All links are now upgraded to https:// when possible (the thumbnail service is still http:// as it doesn't support https://).
Updated by Krasnaya Ploshchad’ over 5 years ago
Once we made the implementation, I think we should also make improves in LibreOffice to make it support HTTPS/2 accessing, especially for updating and crash bug reports.
Updated by Florian Effenberger almost 5 years ago
- Status changed from New to Closed
Perfect, so closing this :)
Updated by Florian Effenberger almost 5 years ago
Florian Effenberger wrote:
Perfect, so closing this :)
Hm, interesting, this is the reply I added to #2321 actually, not to this ticket... seems the "duplicate" status automatically closes this too