<div dir="ltr">To further confuse matters, when I visit <a href="http://gaares.org:443/">http://gaares.org:443/</a> I receive the "Bad Request" message with Chrome and IE on Server 2008 R2. Seems to me like Apache is just doing whatever it feels like :P <a href="http://bit.ly/1QA6blm">http://bit.ly/1QA6blm</a></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 14, 2016 at 4:02 AM, Ben Coleman <span dir="ltr"><<a href="mailto:oloryn@benshome.net" target="_blank">oloryn@benshome.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2/13/2016 07:27 PM, Jim Kinney wrote:<br>
> Is it possible the server is using encryption methods now deemed<br>
> unsuitable and some browsers are flagging that as a connection error?<br>
<br>
</span>That was my first thought, also.<br>
<br>
A few more observations:<br>
<br>
1. Here it fails on FF on both Win 10 and Ubuntu 15.10, but the error<br>
is different:<br>
<br>
An error occurred during a connection to <a href="http://gaares.org" rel="noreferrer" target="_blank">gaares.org</a>. SSL received a<br>
record that exceeded the maximum permissible length. (Error code:<br>
ssl_error_rx_record_too_long)<br>
<br>
2. If you're on Ubuntu 14.04, there was an Apache update on about Jan<br>
27 or 28. Could the problem have started after that upgrade was applied?<br>
<br>
3. I also note (as did Allen) that going to <a href="http://gaares.org:443/" rel="noreferrer" target="_blank">http://gaares.org:443/</a><br>
returns a valid page, but it looks to me like it's returning the parent<br>
of the default page (i.e. /var/www). Going into the html directory in<br>
that index produces the Apache2 Ubuntu Default page. This seems to<br>
point to a config error of some kind for <a href="http://gaares.org" rel="noreferrer" target="_blank">gaares.org</a> on port 443. Going<br>
via the ip address (i.e. <a href="http://107.189.47.100:443/" rel="noreferrer" target="_blank">http://107.189.47.100:443/</a> produces the<br>
expected "Bad Request] Your browser sent a request that this server<br>
could not understand. Reason: You're speaking plain HTTP to an<br>
SSL-enabled server port. Instead use the HTTPS scheme to access this<br>
URL, please." (which is what you would expect to get from<br>
<a href="http://gaares.org:443/" rel="noreferrer" target="_blank">http://gaares.org:443/</a>).<br>
<span class="HOEnZb"><font color="#888888"><br>
Ben<br>
--<br>
Ben Coleman <a href="mailto:oloryn@benshome.net">oloryn@benshome.net</a> | For the wise man, doing right trumps<br>
<a href="http://oloryn.benshome.net/" rel="noreferrer" target="_blank">http://oloryn.benshome.net/</a> | looking right. For the fool, looking<br>
Amateur Radio NJ8J | right trumps doing right.<br>
<br>
</font></span><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br></div>