Hello,
I don't think nginx uses Java key store and that's specific only for
Java applications. you should ask your manufacturer the details on how
your door works.
Also this (nginx-devel@nginx.org) mailing list is specifically for
developers to discuss about code/bugfix/features and not for probl
2516641#0: malloc: 55ADC46D9520:8
2024/01/13 15:19:44 [debug] 2516641#0: notify eventfd: 9
2024/01/13 15:19:44 [debug] 2516641#0: testing the EPOLLRDHUP flag: success
2024/01/13 15:19:44 [debug] 2516641#0: malloc: 000055ADC47073D0:6144
2024/01/13 15:19:44 [debug] 2516641#0: malloc: 7F4DF059E010:25
05:59 [debug] 2452969#0: *17 post access phase: 9
2024/01/13 15:05:59 [debug] 2452969#0: *17 generic phase: 10
2024/01/13 15:05:59 [debug] 2452969#0: *17 generic phase: 11
2024/01/13 15:05:59 [debug] 2452969#0: *17 http init upstream, client timer: 0
2024/01/13 15:05:59 [debug] 2452969#0: *17 epoll a
7 generic phase: 11
2024/01/13 15:05:59 [debug] 2452969#0: *17 http init upstream, client timer: 0
2024/01/13 15:05:59 [debug] 2452969#0: *17 epoll add event: fd:3 op:3
ev:80002005
Thank you Maxim for answering my questions!
On Sat, Jan 13, 2024 at 6:23 AM Maxim Dounin wrote:
>
> He
"-d ''"
I do doing it at NGX_HTTP_ACCESS_PHASE in the handler. It seems that
if "content_length = 0", it skips the access phase handler as well?
Does this have to do with what we discussed?
On Fri, Jan 12, 2024 at 5:59 AM Maxim Dounin wrote:
>
> Hello!
>
&g
,
ngx_http_foo_body_handler);
if (rc >= NGX_HTTP_SPECIAL_RESPONSE) {
return rc;
}
Can i buy you coffee?
Thank you!
On Thu, Jan 11, 2024 at 1:06 PM Muhammad Nuzaihan wrote:
>
> Hi Maxim,
>
> Sorry for asking too many questions.
>
> I did looked at he mirror module and i c
dules/ngx_http_mirror_module.c
I'm going with point 1. I know it will break proxying but it's more
simpler and i can think of doing 2. later on.
Thank you,
Zaihan
On Thu, Dec 21, 2023 at 8:59 AM Maxim Dounin wrote:
>
> Hello!
>
> On Tue, Dec 19, 2023 at 10:11:04PM +0800, Muhammad N
errors.
Handlers can only handle (from what i know) URL path and headers.
Request body requires a request chain (ngx_chain_t)) to piece out the
request body and handlers doesn't seem to have t ngx_chain_t unlike
request body filters.
Or maybe i am wrong in this case?
Thank you,
Muhammad Nuz
Hi,
Sorry about the previous email. I meant
ngx_http_top_request_body_filter is not executed whenever there is no
body.
Thank you,
Muhammad Nuzaihan
On Wed, Dec 13, 2023 at 3:55 PM Muhammad Nuzaihan wrote:
>
> Hi,
>
> I need to process requests with only URI path (without body)
,
Muhammad Nuzaihan
___
nginx-devel mailing list
nginx-devel@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx-devel
Hi,
I would like to return an error message based on the *response* body.
I know i can do it easily with *request* body (with "return
NGX_HTTP_BAD_REQUEST") but my case i want to do it with *response*
body.
Also i have tried this code with response body filter but i got "*1
header already sent,
11 matches
Mail list logo