Hi all,
It seems that when using HttpAccessModule directives to deny requests, they
don't seem to work if the server is listening on a unix domain socket. Even
when using deny all.
Can someone confirm and it's not just me making some stupid mistake ?
Now if that is the case, would it be a good id
onnections that come through all unix
domain sockets ?
Thank you.
2013/5/22 Maxim Dounin
> Hello!
>
> On Tue, May 21, 2013 at 10:27:21PM +0300, Sorin Manole wrote:
>
> > Hi all,
> >
> > It seems that when using HttpAccessModule directives to deny requests,
> they
Hello fellow nginxers,
>From searching the Internet I gathered that proxying requests to a backend
without buffering the whole body wasn't available at the time the question
was asked. Is still the case?
If yes, is this a limitation of the nginx core (lack of implementation of a
phase for request
same question stands still, is there a
reason a patch like this isn't integrated into the mainline?
Thank you.
2014-02-06 15:06 GMT+02:00 Weibin Yao :
> You may looks at the patch I wrote as an example
> (http://yaoweibin.cn/patches/). Thank you.
>
> 2014-02-05 23:33 GMT+08:00 So
Hello,
It seems that if the client closes the connection during a requests there
are time when the request is logged as 400 and other times as 499.
Is there a reason for the difference? Serving of the error page cannot be
it because the connection is closed anyway.
Thanks.
Examples of 400:
http
Hello,
You need to create a response body filter module. Your filter handler is
called every time some response data is received from the upstream. In that
handler you can use the ngx_write_chain_to_file or
ngx_write_chain_to_temp_file functions to write the data to your file.
An example of such a
Hello,
This doesn't work probably because the request data (headers + body) that
is sent to the upstream is "compiled" before the actual connection is
established.
See http://lxr.nginx.org/source/src/http/ngx_http_upstream.c#0574
->create_request(...) is called before ngx_http_upstream_connect(...)
Hey Maxime! The solution you described makes sense and should work. And
yes, you should probably use HTTP_AUX_FILTER_MODULES to register your
handler.
You will have to do a little more juggling with buffers however. From what
I remember, the default behaviour when using not NGX_HTTP_SUBREQUEST_IN_M
If the data is generated during the requests and there is no way to
precompute it, I guess you best bet would be to generate and feed the data
from a filter handler. Basically, the content handler for a particular
location could be a the empty_gif module, and while the response is sent to
the clien
2015-11-24 22:41 GMT+02:00 Ruslan Ermilov :
> details: http://hg.nginx.org/nginx/rev/b1858fc47e3b
> branches:
> changeset: 6306:b1858fc47e3b
> user: Ruslan Ermilov
> date: Fri Nov 06 15:22:43 2015 +0300
> description:
> Style: unified request method checks.
>
> diffstat:
>
> src/http
ov :
> On Tue, Nov 24, 2015 at 11:31:16PM +0200, Sorin Manole wrote:
> > 2015-11-24 22:41 GMT+02:00 Ruslan Ermilov :
> >
> > > details: http://hg.nginx.org/nginx/rev/b1858fc47e3b
> > > branches:
> > > changeset: 6306:b1858fc47e3b
> > > user:
Would it make sense to add nocacheable if input_var or one of the variables
in the value options is nocacheable?
On Mon, 28 Nov 2016 at 12:58, Eran Kornblau
wrote:
> Hi all,
>
>
>
> I created this post yesterday - https://forum.nginx.org/read.php?10,271197
>
> And thought about submitting a patc
Hello!
>> For the Cache-Control header, the fix is to postpone pushing
>> r->headers_out.cache_control until its value is completed.
Why not do the same thing for a bunch of other places like:
ngx_http_auth_basic_set_realm
ngx_http_range_not_satisfiable
That is, for the latter, first initialize
Hello,
Would you be willing to accept a patch to support CXX and CXXFLAGS in
the nginx build logic?
This could be used to write C++ nginx module code.
I attached a partial implementation. Please confirm if this is the
correct approach.
Thanks.
___
nginx
Missed attachment.
2017-05-21 22:23 GMT+03:00 Sorin Manole :
> Hello,
>
> Would you be willing to accept a patch to support CXX and CXXFLAGS in
> the nginx build logic?
> This could be used to write C++ nginx module code.
> I attached a partial implementation. Please conf
Hello,
Do you think there is a problem in making the set directive available
at http level (right now it's only server and lower). This would allow
the usage of variables defined (and overridden in a lower config
level) by set in directives like "map" and "log_format".
Thanks.
___
Hello,
On some systems the IP_TRANSPARENT feature is available, but the
constant is not defined in glilb.
Can you consider supporting this setup by defining the constant in
nginx itself if missing from glib?
https://unix.stackexchange.com/questions/58431/ip-transparent-missing-from-glibc-headers
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 to be pr
18 matches
Mail list logo