Describe the bug
If you put a reverse proxy in front of open refine, a reverse that speak http2 with the outsite word, openrefile will run very slow for every set of GET requests, and sometimes you will get 503 errors.
If i disable http2, to return to http1.1, the problem disappear.
To Reproduce
Steps to reproduce the behavior:
ssl_certificate /etc/nginx/conf.d/my.cer;
ssl_certificate_key /etc/nginx/conf.d/my.key;
location / {
proxy_pass http://127.0.0.1:3333/;
}
}
`
please note that nginx speaks http2 with the outsite word (browser), but http1.1 with the backend openrefine server (on http://127.0.0.1:3333/).
Current Results
Even the first page is delayed of ~30-50s, sometimes you will get 503 errors.
Expected behavior
Normal loading time of max 3s for the first page.
Workaround
ssl_certificate /etc/nginx/conf.d/my.cer;
ssl_certificate_key /etc/nginx/conf.d/my.key;
location / {
proxy_pass http://127.0.0.1:3333/;
}
}
`
(i've removed the http2).
With these two workaround, openrefine is fast as normal.
Screenshots
Desktop (please complete the following information):
OpenRefine (please complete the following information):
Thanks for the report! I think this should be solved by migrating to a modern web framework.
Disable of http2 from Ngix make sense since http2 only works better/faster when the application use the SSL/TLS:
https://www.nginx.com/blog/7-tips-for-faster-http2-performance/
Also I think there will be some http1.1/http2 conversion occurs which also take time.
In 4.x I have upgraded Butterfly to use Jetty 9 which supports HTTP 2, I am not sure if this will automatically solve this though.
Most helpful comment
Thanks for the report! I think this should be solved by migrating to a modern web framework.