> On 1 Mar 2025, at 18:41, Sorin Manole wrote:
>
> Hello,
>
> Didn't know where to report it, just a small improvement of the development
> guide wording:
>
> The function ngx_event_process_posted() is called to process an event queue.
> It calls event handl
Hi Sorin,
thanks for the report!
On Sat, Mar 01, 2025 at 04:41:15PM +0200, Sorin Manole wrote:
> Hello,
>
> Didn't know where to report it, just a small improvement of the development
> guide wording:
>
> The function ngx_event_process_posted() is called to process an
Hello,
Didn't know where to report it, just a small improvement of the development
guide wording:
The function ngx_event_process_posted() is called to process an event
queue. It calls event handlers until the queue is not empty. This means
that a posted event handler can post more events
Hi,
> Hi,
>
> I've been following the development of the QUIC protocol within Nginx, and I
> am particularly interested in the implementation of advanced congestion
> control algorithms such as BBR and CUBIC.
>
> Considering the impact that these algorithms can h
Hi,
I've been following the development of the QUIC protocol within Nginx, and I am
particularly interested in the implementation of advanced congestion control
algorithms such as BBR and CUBIC.
Considering the impact that these algorithms can have on network performance,
especial
Ok, that did it, was a bit more painful than expected since I had to
actually write a filter function (if you don't provide it, your init
method is also overwritten by the default) but in the end it is now
cleanly processing without hanging up on my upstream daemon.
A suggested change to consider
> Hmmm, hopefully this works because I subscribed with digest. Thank you very
> much for the feedback, I now had an idea of where to focus (I had a rough
> idea but this made it clearer). And now I know what the issue is but have no
> idea how to resolve it.
>
> My module was setting the upst
>
> Message: 2
> Date: Sun, 7 Jun 2020 06:11:24 +
> From: Eran Kornblau
> To: "nginx-devel@nginx.org"
> Subject: RE: General Development Inquiry
> Message-ID:
>
>
>
> Content-Type: text/plain; charset="us-ascii"
>
&
> 2) I'm actually working on a second module/system aside from the one
> mentioned in my previous post. This might actually be an easier question?
> It's using a custom upstream (like the memcache one) to talk a binary
> protocol to another daemon with requests/responses. For the most part it
Giving this one more try with a few questions this time.
1) This mailing list used to be more discussion oriented but seems to
be mainly patch notifications now. Is there a more appropriate
channel to ask these kind of module development questions for NGINX?
2) I'm actually working on a s
Hi Hung,
Thank you for your advice that really sound like much simpler and better
solution!
From: nginx-devel On Behalf Of Hung Nguyen
Sent: Monday, February 18, 2019 3:52 PM
To: nginx-devel@nginx.org
Subject: Re: [Module development] Any good idea to hook response from proxy
As my
As my understanding all you need is doing a body filter on backend_upstream
response and send a set request to memcache with value is response itself.
To determine whether response is from memcache or from backend, before proxy
pass request to backend you can set some customize header like x-up
At very beginning apologizes for the newbie question, but I am very new in
Nginx but would like to extend some functionality in the existing module.
I am currently using ngx_http_enhanced_memcached_module, and it meets most of
my needs.
However, currently, I need to manually populate cache, via
13.02.2017 12:38, Vladimir Homutov пишет:
> Hello all!
>
> We are glad to share with first results of our ongoing efforts to create
> documentation for nginx developers: the development guide document [1].
>
> The guide is not yet 100% complete and more parts to follow.
&g
Hi,
Now I am writing a Nginx module to communicate with an upstream server
(LDAP) . I had coded both the create_request and process_header callback
functions. But the problem is, I don’t want to talk with the upstream for for
all the requests but only for the requests with some special par
Hi,
I'm willing to pay someone familiar with nginx module development to spend
an hour or 2 with me on google hangouts. The easiest method for me is to
send payment via paypal. Is there anyone interested in this?
--
Thanks,
Joe Spencer (member)
Kogo Softwar
Hi,
On Thursday, Jun 8, 2017 0:42 AM +0300, Vladimir Homutov wrote:
>07.06.2017 17:00, 胡聪 (hucc) пишет:
>> Hello,
>>
>> There are two possible errors in
>> http://nginx.org/en/docs/dev/development_guide.html#http_load_balancing
>>
>>> init(r, us) — initializes per-request ngx_http_upstream_peer
07.06.2017 17:00, 胡聪 (hucc) пишет:
> Hello,
>
> There are two possible errors in
> http://nginx.org/en/docs/dev/development_guide.html#http_load_balancing
>
>> init(r, us) — initializes per-request ngx_http_upstream_peer_t.peer (not to
>> be confused with the
>> ngx_http_upstream_srv_conf_t.peer
eam_t.peer object of
type ngx_peer_connection_t:"
-- Original --
From: "Maxim Konovalov";;
Date: Apr 20, 2017
To: "nginx-devel";
Subject: Re: nginx development guide
Hello,
On 13/02/2017 12:38, Vladimir Homutov wrote:
> Hello all!
&
Hello,
On 13/02/2017 12:38, Vladimir Homutov wrote:
> Hello all!
>
> We are glad to share with first results of our ongoing efforts to create
> documentation for nginx developers: the development guide document [1].
>
> The guide is not yet 100% complete and more parts to foll
On Mon, Feb 13, 2017 at 07:24:05PM +0300, Andrey Kulikov wrote:
> Hooray!
>
> What the doctor ordered.
> Looking forward for more parts, especially dedicated to chains
> management and corresponding API description.
>
> So far saw a possible typo:
> In section "I/O events":
> > that the functions n
re with first results of our ongoing efforts to create
> > documentation for nginx developers: the development guide document [1].
> >
> > The guide is not yet 100% complete and more parts to follow.
> >
> > Of course, your feedback is welcome.
> >
> > [1] htt
reate
> documentation for nginx developers: the development guide document [1].
>
> The guide is not yet 100% complete and more parts to follow.
>
> Of course, your feedback is welcome.
>
> [1] http://nginx.org/en/docs/dev/development_guide.html
> ___
ocumentation for nginx developers: the development guide document [1].
>
>The guide is not yet 100% complete and more parts to follow.
>
>Of course, your feedback is welcome.
>
>[1] http://nginx.org/en/docs/dev/development_guide.html
>___
>n
Hello all!
We are glad to share with first results of our ongoing efforts to create
documentation for nginx developers: the development guide document [1].
The guide is not yet 100% complete and more parts to follow.
Of course, your feedback is welcome.
[1] http://nginx.org/en/docs/dev
Hello all,
I’m trying to build a nginx module both with C code and Go code. The idea is to
create a Go code that is compiled into a shared library and then call function
of this lib from a basic nginx module C code.
Here is my handler (in C), taken from this guide:
https://www.airpair.com/ngin
Hello there,
I'm in the process of writing a custom nginx module that should do some header
manipulation and some logging of strings created in that manipulation process.
The module/nginx then proxies the requests to another backend...
So far I have implemented a handler function that does th
On 8/21/14 3:14 PM, Richard Fussenegger, BSc wrote:
> Many thanks to Paulo, Ruslan and oscaretu for all the answers. I'll
> dig deep and will most certainly open up new threads with questions
> regarding the features I wish to implement.
>
> If someone has anything else of interest to share, don't
aulo Silva wrote:
Hi Richard,
I am also new to nginx development and the best resource, so far are:
* http://www.evanmiller.org/nginx-modules-guide.html
* http://antoine.bonavita.free.fr/nginx_mod_dev_en.html
I met a guy, Wandenberg Peixoto ( https://github.com/wandenberg) who
has been an inval
On Wed, Aug 20, 2014 at 07:48:34PM +0200, Richard Fussenegger, BSc wrote:
> I'd like to start working on the nginx source. I know my way around in C
> (although I'm not a crack at all) but I'm totally new to nginx. Do you
> have some starting points that would help a new developer to understand
Hi Richard,
I am also new to nginx development and the best resource, so far are:
* http://www.evanmiller.org/nginx-modules-guide.html
* http://antoine.bonavita.free.fr/nginx_mod_dev_en.html
I met a guy, Wandenberg Peixoto ( https://github.com/wandenberg) who has
been an invaluable help.
I
Hi!
I'd like to start working on the nginx source. I know my way around in C
(although I'm not a crack at all) but I'm totally new to nginx. Do you
have some starting points that would help a new developer to understand
how things work?
- Coding standards (already noticed an 80 character har
Hello!
On Tue, Jul 01, 2014 at 03:30:43PM +0100, David Carlier wrote:
> What if I look into this one http://trac.nginx.org/nginx/ticket/485
>
> This kind of change in the ngx_http_request_t struct will be accepted (and
> furthermore auth basic module, upstream ...) ??
I've responded in the tick
Hi Filipe,
What if I look into this one http://trac.nginx.org/nginx/ticket/485
This kind of change in the ngx_http_request_t struct will be accepted (and
furthermore auth basic module, upstream ...) ??
Thanks in advance.
On 30 June 2014 09:05, Filipe Da Silva wrote:
> Hi,
>
> In short : http
Hi,
In short : http://nginx.org/en/docs/contributing_changes.html
And, patch must be made with this option set in your hgrc file :
[diff]
showfunc = True
Rgds,
Filipe
2014-06-28 8:22 GMT+02:00 David Carlier :
> HI All,
> I am working as C/C++ developer for a company which makes nginx modules a
HI All,
I am working as C/C++ developer for a company which makes nginx modules and
would like to know if I can contribute a bit.
Kind regards.
David CARLIER
dotMobi / Afilias Technologies DUBLIN
___
nginx-devel mailing list
nginx-devel@nginx.org
http:/
36 matches
Mail list logo
