Nginx 1.4 problem

[Alder Network]

I tried
  listen [::]:80 ipv6only=off;
and the TCP connection went through, but got
an http 400 bad response.

It would be nice to have a corresponding config
upgrade manual as well.  Thanks,



On Wed, May 1, 2013 at 2:18 PM, Paul N. Pace <paulnpace at gmail.com> wrote:

> On Wed, May 1, 2013 at 2:07 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> > Hello!
> >
> > On Wed, May 01, 2013 at 11:17:10AM -0700, Alder Network wrote:
> >
> >> Just for clarity, I want to be listening on both IPv4 and IPv6 on the
> same
> >> port.
> >
> > You have to write
> >
> >     listen 80;
> >     listen [::]:80;
> >
> > to listen on both IPv4 and IPv6.
>
> Doesn't that require ipv6only=on?
>
>      listen 80;
>      listen [::]:80 ipv6only=on;
>
>
> >
> >>
> >>
> >> On Wed, May 1, 2013 at 11:00 AM, Alder Network <aldernetwork at gmail.com
> >wrote:
> >>
> >> > netstat -pln shows the server is waiting on that port.
> >> >
> >> > Yes, I have been using in server section
> >> >     listen [::]:80;
> >> > What is supposed to be for IPV4 now?
> >> >
> >> > I'll go over the changelist later, Thanks,
> >> >
> >> > - Alder
> >> >
> >> >
> >> > On Wed, May 1, 2013 at 10:40 AM, Maxim Dounin <mdounin at mdounin.ru>
> wrote:
> >> >
> >> >> Hello!
> >> >>
> >> >> On Wed, May 01, 2013 at 10:13:34AM -0700, Alder Network wrote:
> >> >>
> >> >> >   Tried to upgrade to just-released Nginx1.4. TCP 3-way hand-shake
> >> >> > aborted by server's ACK+RST packet, but netstat shows server
> >> >> > is listening on that port. Any config has been changed since Nginx
> 1.2
> >> >> > to 1.4 in this regard?
> >> >>
> >> >> There are lots of changes in 1.4.0 compared to 1.2.x, see
> >> >> http://nginx.org/en/CHANGES-1.4.
> >> >>
> >> >> In this particular case I would recommend checking if nginx is
> >> >> listening on the port, the address, and the protocol in question.
> >> >> Note that since 1.3.4 ipv6only listen option is on by default, and
> >> >> if you have
> >> >>
> >> >>     listen [::]:80;
> >> >>
> >> >> in your config, it no longer implies IPv4 addresses regardless of
> >> >> your OS settings.
> >> >>
> >> >> --
> >> >> Maxim Dounin
> >> >> http://nginx.org/en/donation.html
> >> >>
> >> >> _______________________________________________
> >> >> nginx mailing list
> >> >> nginx at nginx.org
> >> >> http://mailman.nginx.org/mailman/listinfo/nginx
> >> >>
> >> >
> >> >
> >
> >> _______________________________________________
> >> nginx mailing list
> >> nginx at nginx.org
> >> http://mailman.nginx.org/mailman/listinfo/nginx
> >
> >
> > --
> > Maxim Dounin
> > http://nginx.org/en/donation.html
> >
> > _______________________________________________
> > nginx mailing list
> > nginx at nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130501/de16195b/attachment.html>