Should use the user-provided Host header for SNI

I’m trying to test Apache configuration in a Vagrant VM that forwards port 8443 to VM’s port 443. The command I’m running is:

$ http get https://localhost:443/ Host:www.example.com --verify=no

and I get a 400 Bad Request from Apache, because

[Mon Nov 23 09:43:17 2015] [error] Hostname localhost provided via SNI and hostname www.example.com provided via HTTP are different

I think httpie should use the user-provided Host header for the SSL negotiation, or perhaps even provide a command-line option to explicitly specify a hostname to use in SNI.

[fdcds]

gnutls-cli has the --sni-hostname=... option. It would be great to have that for http too, and it would prevent unexpected effects when re-using the value of a header for a different purpose (TLS and HTTP live on different OSI layers, so should be treated independently).

[mgedmin]

Good point about cookies! What about

http get https://foo.example.com/ --connect-to 127.0.0.1:8443

then?

I don’t like curl’s --resolve solution (aka #362) because it requires me to repeat the host name, which is unnecessary in 99% of use-cases. (It’s probably necessary if you want to follow redirects to a different domain name, that you’re also testing in Vagrant or something like that.)

I don’t like the /etc/hosts solution because:

• it requires root
• it affects the entire system, not just my little experimental shell session
• it’s persistent and I have to remember to undo any testing changes I make