Dear members,
To achieve my usecase, i have created a module that launches two subrequests to different upstreams. I then retrieve the body of those subrequests' responses and put them into a single output chain. Which i forward to a dedicated filter.
This works sometimes, and sometimes not ... Indeed, NGINX worker regularly crashes during request finalization, the reason for this is that the request pool is NULL (as many of the ngx_http_request_t attributes). I suspect it has been freed by some way but i don't get why it doesn't happen everytime
If you have any ideas ?
Thanks,
kR
To achieve my usecase, i have created a module that launches two subrequests to different upstreams. I then retrieve the body of those subrequests' responses and put them into a single output chain. Which i forward to a dedicated filter.
This works sometimes, and sometimes not ... Indeed, NGINX worker regularly crashes during request finalization, the reason for this is that the request pool is NULL (as many of the ngx_http_request_t attributes). I suspect it has been freed by some way but i don't get why it doesn't happen everytime
If you have any ideas ?
Thanks,
kR