On Mon, Mar 11, 2019 at 1:16 PM Igor Sysoev wrote:
> Today is an important day for NGINX. We signed an agreement to join to F5.
>
> The NGINX team and I believe this is a significant milestone for our
> open source technology, community, and the company.
>
> F5 is committed to our open source mis
On Fri, Jun 17, 2016 at 2:48 PM, jordan.davidson <
nginx-fo...@forum.nginx.org> wrote:
> We need TCP (not http) hostname routing for an environment we are creating
> using k8s and ingress with the nginx ingress controller. We are trying to
> figure out if there is a way to create an nginx server w
On Fri, Jun 20, 2014 at 5:20 AM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Jun 20, 2014 at 10:51:38AM +0200, Yifeng Wang wrote:
>
> > Hi, It's my first time using NGINX to proxy other web servers. I set a
> > variable in location, this variable may be gotten in cookie or args. if
> > I use it dire
On Wed, Apr 30, 2014 at 12:55 AM, Lukas Tribus wrote:
> Hi,
>
>
> >> The fix is already in OpenBSD [4], Debian and Ubuntu will probably ship
> the
> >> patch soon, also see [5] and [6].
> >
> > Oh, cool, that's good news that it's upstream then. Getting the patch
> > to apply is a piece of cake.
On Tue, Apr 29, 2014 at 4:36 PM, Lukas Tribus wrote:
> Hi Mark,
>
>
> > I'm running into a lot of the same error as was reported in the forum
> > at:
> http://mailman.nginx.org/pipermail/nginx-devel/2013-October/004385.html
> >
> >> SSL: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption fail
I'm running into a lot of the same error as was reported in the forum at:
http://mailman.nginx.org/pipermail/nginx-devel/2013-October/004385.html
> SSL: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad
record mac
I've got an nginx server doing front-end SSL, with the upstream
On Thu, Jun 20, 2013 at 2:00 AM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Jun 19, 2013 at 11:06:19AM -0700, Mark Moseley wrote:
>
> > TL;DR:
> > Any nginx setting to say 'if a vhost's ssl settings are broken, skip it
> and
> > don't fail to start&
TL;DR:
Any nginx setting to say 'if a vhost's ssl settings are broken, skip it and
don't fail to start' ?
I've certainly RTFM'd this and peered at the source, but I figured I might
as well throw it out there, in case there's some hidden setting I've missed.
I'm building a reverse proxy config for
