Creating a tracking ticket so I can keep all the research and planning related to this in one place.
Jellyfish currently doesn't support HTTPS, and a good stopgap until we get it working is to just let https traffic pass through. At the moment we seem to be closing https requests with an empty response (Chrome: Error 324 (net::ERR_EMPTY_RESPONSE))
To support HTTPS we need to address:
- Certs. Jellyfish is essentially a man in the middle attack, so we need to self sign each host the proxy deals with and have a mechanism for the browser to accept the cert.
- Adding the https server port to each browser setup vars.
Creating a tracking ticket so I can keep all the research and planning related to this in one place.
Jellyfish currently doesn't support HTTPS, and a good stopgap until we get it working is to just let https traffic pass through. At the moment we seem to be closing https requests with an empty response (Chrome: Error 324 (net::ERR_EMPTY_RESPONSE))
To support HTTPS we need to address:
- Certs. Jellyfish is essentially a man in the middle attack, so we need to self sign each host the proxy deals with and have a mechanism for the browser to accept the cert.