<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">
<pre wrap="">You will need at least a proper ssl configuration in that server{}
block -- possibly setting it at http level.
</pre>
</blockquote>
that makes sense. thanks again!<br>
<br>
<div class="moz-signature">
<p>Igal Sapir
<br>
Lucee Core Developer
<br>
<a href="http://lucee.org/">Lucee.org</a></p>
</div>
<div class="moz-cite-prefix">On 8/21/2015 12:30 AM, Francis Daly
wrote:<br>
</div>
<blockquote cite="mid:20150821073008.GG23844@daoine.org" type="cite">
<pre wrap="">On Thu, Aug 20, 2015 at 11:35:58PM -0700, Igal @ Lucee.org wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 8/20/2015 3:55 PM, Igal @ Lucee.org wrote:
</pre>
</blockquote>
<pre wrap="">
Hi there,
I do not know the full answer to your question.
</pre>
<blockquote type="cite">
<pre wrap="">when I tried to add listen for port 443 it broke the https for requests
with the valid hostname as well.
## disable http server for requests with unknown hosts
server {
listen IP:80 default_server;
# listen IP:443 default_server; # breaks all https??
return 444;
}
what's the trick to do the same for https without breaking the requests
for <a class="moz-txt-link-freetext" href="https://myhost/">https://myhost/</a> ?
</pre>
</blockquote>
<pre wrap="">
You will need at least a proper ssl configuration in that server{}
block -- possibly setting it at http level.
See, for example,
<a class="moz-txt-link-freetext" href="http://nginx.org/en/docs/http/configuring_https_servers.html#name_based_https_servers">http://nginx.org/en/docs/http/configuring_https_servers.html#name_based_https_servers</a>
In general, the ssl hostname that the browser wants to connect to is
not available until after the ssl negotiation has happened.
f
</pre>
</blockquote>
<br>
</body>
</html>