On 05/12/2016 17:12, Maxim Dounin wrote:
Hello!
On Mon, Dec 05, 2016 at 02:40:27PM +, Steven Hartland wrote:
On 05/12/2016 13:27, Maxim Dounin wrote:
Hello!
On Sun, Dec 04, 2016 at 09:39:59PM +, Steven Hartland wrote:
[...]
I believe the change to add a localhost bind to the serve
Hello :-)
Maxim Dounin Wrote:
---
> Yes, but there isn't much difference: as long as httpready sees
> something different from a HTTP request, it just passes the
> connection to nginx.
>
> Quoting accf_http(9):
>
> If something other tha
Hello!
On Wed, Dec 14, 2016 at 06:36:14AM -0500, Alt wrote:
> steveh Wrote:
> ---
>
> > listen 443 default_server accept_filter=httpready ssl;
> > listen 80 default_server accept_filter=httpready;
>
> Not related to your problem: I think you'l
Hello !
steveh Wrote:
---
> listen 443 default_server accept_filter=httpready ssl;
> listen 80 default_server accept_filter=httpready;
Not related to your problem: I think you'll want "accept_filter=dataready"
for your SSL configuration.
Best
On 05/12/2016 17:12, Maxim Dounin wrote:
Hello!
On Mon, Dec 05, 2016 at 02:40:27PM +, Steven Hartland wrote:
snip...
Given that the real local address of the listening socket as shown
by netstat is 10.10.96.146, it means that the socket was created
when there were no explicit 127.0.0.1 in
Hello!
On Mon, Dec 05, 2016 at 02:40:27PM +, Steven Hartland wrote:
> On 05/12/2016 13:27, Maxim Dounin wrote:
> > Hello!
> >
> > On Sun, Dec 04, 2016 at 09:39:59PM +, Steven Hartland wrote:
[...]
> >> I believe the change to add a localhost bind to the server in question
> >> was relat
On 05/12/2016 13:27, Maxim Dounin wrote:
Hello!
On Sun, Dec 04, 2016 at 09:39:59PM +, Steven Hartland wrote:
We've used nginx for years and never had an issue with nginx upgrade
until today where the upgrade command ran but almost instantly after the
new process exited.
/usr/local/etc/rc.
Hello!
On Sun, Dec 04, 2016 at 09:39:59PM +, Steven Hartland wrote:
> We've used nginx for years and never had an issue with nginx upgrade
> until today where the upgrade command ran but almost instantly after the
> new process exited.
>
> /usr/local/etc/rc.d/nginx upgrade
> Performing san
We've used nginx for years and never had an issue with nginx upgrade
until today where the upgrade command ran but almost instantly after the
new process exited.
/usr/local/etc/rc.d/nginx upgrade
Performing sanity check on nginx configuration:
nginx: the configuration file /usr/local/etc/nginx/
