Add support and test coverage for running in environments with HTTP/2 Restrictions

[jwmatthews]

This issue is tracking a need to ensure that the Solution Server (and any future components) we add to Kai are able to run in enterprise environments which restrict HTTP/2 usage.

This should become part of test coverage to protect against future regressions.

See konveyor/editor-extensions#1030

[jmontleon]

You can run mitmweb --set http2=false --mode wireguard on another system.

Stop your firewall or otherwise ensure port 51820 is accessible on your proxy host
(probably sudo firewall-cmd add-port 51820/udp is fine but I didn't test yet)

On the capture tab it'll show you a wireguard config (I think you can find this as wireguard.conf in ~/mitmproxy as well, probably useful if running mitmproxy instead of mitmweb), copy it to a file on the system you're running code / kai. I used the name wg0.conf
Import it into NetworkManager

nmcli con import type wireguard file wg0.conf

For me the connection starts right up.

You'll probably want to copy ~/.mitmproxy/mitmproxy-ca-cert.pem from your proxy host to your code / kai system at /etc/pki/ca-trust/source/anchors/ and run sudo update-ca-trust otherwise everything is going to barf with ssl errors. Alternatively NODE_TLS_REJECT_UNAUTHORIZED=0 code will work for code alone.

[jmontleon]

To not have to use NODE_TLS_REJECT_UNAUTHORIZED=0 I had to enable the experimental System Certificates V2 option.

[jmontleon]

My instructions are for Fedora on both proxy and code host. They will likely need adjusting for other distros and operating systems

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 60 days.
It will remain open for visibility and reporting purposes.
Please comment if this issue is still relevant.