Re: [users@httpd] Cannot authenticate (after six years)

Because you are not using encryption, I hope that you know anyone on your network can sniff your login usernames and passwords used for your webserver. You can get a free SSL certificate from: https://letsencrypt.org/ You can test your SSL server here: https://www.ssllabs.com/ssltest/analyze.html

Re: [users@httpd] How can I force a server name header?

http://ip/ will always land on the default (first) vhost unless you have another vhost with ServerName IP set. Just set up an arbitrary hostname to resolve to 192.168.1.7, then use http://dummyhostname/. Make sure to define a vhost with that ServerName set as well. I would encourage you to look at

[users@httpd] How can I force a server name header?

I'm trying to test a new server located at internal IP 192.168.1.5. The production server lives at IP 192.168.1.7 on the same network. How can I force the browser to connect to the correct server? If I try "http://192.168.1.5"; the redirect on the first (alphabetically) virtual server redirect