nginx + DSCP (Differentied services)

2014-12-16 Thread Dani Bento
e the class id to use. Do you find this an interesting feature to add to the nginx core? How can we proceed and submit a patch? Thanks, Dani -- Dani Bento Direção de Internet e Tecnologia DTS/DVS tlm: +351 91 429 72 81 d...@telecom.pt ___ nginx-

Re: nginx + DSCP (Differentied services)

2014-12-16 Thread Dani Bento
on a static configuration. Can it be set by variable "tos $class_id" ? It may be interesting to merge our patch with your module... Dani On Tue, 16 Dec 2014 15:46:36 + Maxim Dounin wrote: > Hello! > > On Tue, Dec 16, 2014 at 02:21:59PM +, Dani Bento wrote: > >

Re: nginx + DSCP (Differentied services)

2014-12-17 Thread Dani Bento
> You can only have one ToS mark for > > each location if you relying on a static configuration. Can it be > > set by variable "tos $class_id" ? > > Not now, but this can be added if needed - like it was recently > added to the "expires" directive, see >

Re: nginx + DSCP (Differentied services)

2015-02-04 Thread Dani Bento
Hello, Any advance on this idea? Or it will be easier to adapt Maxim's module to do what we want? (mainly IPv6 compatibility and the possibility to change DSCP mark via backend header interaction). Thanks. Dani On Wed, 17 Dec 2014 11:27:29 + Dani Bento wrote: > Hello, > >

nginx report a timestamp on upstream_response_time

2015-02-10 Thread Dani Bento
ave we any way to avoid those pikes in the logs? Dani -- Dani Bento Direção de Internet e Tecnologia DTS/DVS tlm: +351 91 429 72 81 d...@telecom.pt ___ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel

Re: nginx report a timestamp on upstream_response_time

2015-02-10 Thread Dani Bento
+ Maxim Dounin wrote: > Hello! > > On Tue, Feb 10, 2015 at 11:54:57AM +0000, Dani Bento wrote: > > > Hello, > > > > We are using nginx 1.6.2 and we found in our logs a strange behavior > > when connecting to an upstream. > > > > We found that

Re: nginx report a timestamp on upstream_response_time

2015-02-10 Thread Dani Bento
not NULL or 0, it's possible that, in this particular condition, the time will be never updated with the correct value in the ngx_http_upstream_finalize_request? Dani On Tue, 10 Feb 2015 16:08:06 + Dani Bento wrote: > Hello, > > We are using LUA header filter to process so

Re: nginx report a timestamp on upstream_response_time

2015-02-11 Thread Dani Bento
Our problem is that in the log we have: [200 : 302] (for the status codes) [0.02 : 1423667767.600] (for the upstream_response_time) Dani On Tue, 10 Feb 2015 18:10:44 + Maxim Dounin wrote: > Hello! > > On Tue, Feb 10, 2015 at 05:51:46PM +, Dani Bento wrote:

Re: nginx report a timestamp on upstream_response_time

2015-02-11 Thread Dani Bento
ginx-module? Or some nginx race condition? Dani On Wed, 11 Feb 2015 15:26:59 + Maxim Dounin wrote: > Hello! > > On Wed, Feb 11, 2015 at 03:20:59PM +, Dani Bento wrote: > > > Hello, > > > > I was looking in ngx_http_upstream_response_time_variable. > >

nginx-log-zmq module

2015-04-23 Thread Dani Bento
Hello, We recently wrote a nginx module (https://github.com/sapo/nginx-log-zmq) and it may be interesting to add it to the 3rd Party Modules page. It's possible? What we have to do to put our information there? Thanks, Dani -- Dani Bento Direção de Internet e Tecnologia DTS/DVS tlm: +3

Add support for Log ZMQ 3rd Party Module on vim syntax

2016-04-28 Thread Dani Bento
# HG changeset patch # User Daniela Bento # Date 1461886571 -3600 # Fri Apr 29 00:36:11 2016 +0100 # Node ID 6a1f953371d22ab082f05b5249d29ec72f934411 # Parent 2f98b5709d7965e7c97cb74b8380014179c7bf0d Contrib: add support for Log ZMQ on Vim Syntax Add support for the 3rd party module Log ZMQ

Re: Add support for Log ZMQ 3rd Party Module on vim syntax

2016-04-30 Thread Dani Bento
pr 29, 2016 at 11:47 AM, Aleksandar Lazic wrote: > Hi Dani. > > Am 29-04-2016 01:43, schrieb Dani Bento: > >> # HG changeset patch >> # User Daniela Bento >> # Date 1461886571 -3600 >> # Fri Apr 29 00:36:11 2016 +0100 >> # Node ID 6a1f9