Please advise as after upgrading to 8.13.0, I can see warning for Modern HTTP.
We use Reverse HTTPs proxy and tried to use RH8.2 VM that has http2 installed
Still I get a warning have anyone manged to fix that warning
My file is
# cat /etc/httpd/conf.d/apache-proxy.conf
Protocols h2
<VirtualHost *:443>
ServerName myserver.doman
ProxyRequests Off
<Proxy *>
Require all granted
</Proxy>
ProxyPass /jira http://myjira.domain:8080/jira
ProxyPassReverse /jira http://myjira.domain:8080/jira
SSLEngine On
SSLCertificateFile /etc/httpd/conf.d/ServerCertificate.crt
SSLCertificateKeyFile /etc/httpd/conf.d/server.key
SSLCertificateChainFile /etc/httpd/conf.d/ChainBundle.crt
</VirtualHost>
<VirtualHost *:80>
ServerName myserver.domain
Redirect Permanent /jira https://myserver.domain/jira
</VirtualHost>
After discussing with some community champions ( @Matt Doar ) three is an open suggestion for this : https://jira.atlassian.com/browse/JRASERVER-70517.
For my case I will follow Matt advise and disable this health check (healthcheck.http.name (pageProtocolsHealthCheck)).
That ticket is unrelated to how the health check works. The warning pops up only on Jira/Confluence versions that have HTTP/2 working, exhibit network problems and have misconfigured reverse proxy. Disabling it is not advisable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just an update
old warning
Your content is served using outdated HTTP protocols. We recommend
serving pages using HTTP/2 or newer to improve performance for users.
Your navigation protocol is HTTP/1.1 and the resource protocol is HTTP/1.1.
after using h2 protocol new warn
Your content is served using outdated HTTP protocols. We recommend
serving pages using HTTP/2 or newer to improve performance for users.
Your navigation protocol is H2 and the resource protocol is HTTP/1.1.
I dont know where or how to edit resource protocol to H2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Facing the same issue. Have you found a solution for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In your case the problem is different because you have a mix of protocols. The healthcheck is based on the most recent 1000 page views, so depending on the traffic on your instance, it may still report old data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are right. The error message disappeared now. Thank you for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.