Апр 2016 г. 11:41 пользователь "Andrew Hutchings"
> написал:
>
> Hi,
>>
>> Or you could use UUIDv1 and then it would also give you uniqueness and
>> the ability to have some debugging of IDs if required.
>>
>> Kind Regards
>> Andrew
>>
>> On
Hi,
We have been using something like this for ~2 years.
For ours we used a random number to start and the Process ID & Process
start time to try and increase uniqueness between reloads (ours is a 128bit
ID). Then applying an increment, with future requests having a higher id.
Perhaps that would
Thanks, that's what I was using.
On Thu, 4 Feb 2016, 6:30 p.m. Yichun Zhang (agentzh)
wrote:
> Hello!
>
> On Wed, Feb 3, 2016 at 7:09 PM, SplitIce wrote:
> > What is the appropriate way to allocate memory during the stream? The
> http
> > context has a pool
Hey All again,
Quick Question regarding the Stream Module.
What is the appropriate way to allocate memory during the stream? The http
context has a pool member as part of the request structure, what is the
equivalent in the stream module context?
Thanks in Advance,
Mathew
___
The map module is also a noticeable omission tied into the lack of
variables.
On Thu, Feb 4, 2016 at 11:13 AM, Yichun Zhang (agentzh)
wrote:
> Hello!
>
> On Wed, Feb 3, 2016 at 3:37 PM, SplitIce wrote:
> > I have been taking a look at the Stream modules for use in a particular
Hi All,
I have been taking a look at the Stream modules for use in a particular
application. I noticed the entire subsystem lacks any variable support.
- Is variable support planned?
- Is there a significant reason for the omission?
Regards,
Mathew
Issue found.
If worker_processes is set at the start of the config file the feature
works fine, if it is set at the end of the config file it does not.
On Wed, Nov 25, 2015 at 9:38 AM, SplitIce wrote:
> Ok,
>
> I have found it to be a configuration bug. With a fresh configuration
&
bug.
I will update when I know more.
On Wed, Nov 25, 2015 at 12:42 AM, Valentin V. Bartenev
wrote:
> On Wednesday 25 November 2015 00:25:19 SplitIce wrote:
> > Hi all,
> >
> > I couldn't find anything in the mailing list about this issue, surely we
> > ar
at 12:42 AM, Valentin V. Bartenev
wrote:
> On Wednesday 25 November 2015 00:25:19 SplitIce wrote:
> > Hi all,
> >
> > I couldn't find anything in the mailing list about this issue, surely we
> > are not the only one?
> >
> > When activating reusepo
wrote:
> On Wednesday 25 November 2015 00:25:19 SplitIce wrote:
> > Hi all,
> >
> > I couldn't find anything in the mailing list about this issue, surely we
> > are not the only one?
> >
> > When activating reuseport I am seeing all requests be served from
Hi all,
I couldn't find anything in the mailing list about this issue, surely we
are not the only one?
When activating reuseport I am seeing all requests be served from a single
nginx process. All others are just idling (SIGALARM interruption of
epoll_wait / epoll_wait timeout according to strace
In case its relevant we have been running a very similar patch Nils since
the introduction of the syslog feature.
Since the default and expected format on the /dev/log socket is to write
without hostname perhaps unix socket should default to hostname=0 ?
On Wed, Oct 28, 2015 at 6:21 AM, Nils Herm
Hi All,
Yesterday we discovered a possible compatibility issue with a certain
configuration, HTTP2 and Firefox. This configuration works successfully in
Chrome and other HTTP2 enabled browsers, however Firefox users are unable
to connect (connection reset).
The pertinent part of the configuration
Shortly after sending my response I found the commit for BoringSSL adding
the function.
https://boringssl.googlesource.com/boringssl/+/4d4bff89bb8ec345d289412f0f7f135c6e51b1a6%5E!/
On Thu, May 28, 2015 at 2:43 AM, W-Mark Kubacki
wrote:
> 2015-05-05 15:39 GMT+02:00 chen :
> >
> > This is v1 of t
Mark,
>From memory SSL_CIPHER_is_AES is a BoringSSL addition isnt it? I did a
quick look over the OpenSSL source and it does not seem like its been added
either.
I havent had a chance to compile this yet to confirm it, but if correct
then this is not compatible with OpenSSL and possibly other SSL
Good Job.
Perhaps rather than changing the constants, they could be exposed as
configuration options?
On Wed, May 13, 2015 at 12:28 PM, chen wrote:
> 1) we will have that fixed
> 2) no api is exposed by openssl that we can use to trigger a FLUSH, use
> SSL_write is what we can do. If we inspect
You appear to be behind a proxy, look at the output -
http://10.254.40.54:15871/cgi-bin/blockpage.cgi?ws-session=3162698151
Nothing really to do with nginx.
On Sat, Jan 3, 2015 at 4:10 PM, Yugal Mullick
wrote:
> Hi Team,
>
>
>
> Getting below error while downloading and extracting Nginx.
>
>
>
Is it just me or would access_records be per worker and hence this module
not work with workers > 1 ?
Additionally
for (i = 0; i < NGX_HTTP_KNOCK__IP_DB_SIZE && i <
ngx_http_knock_next_free_slot; i++) {
if (access_records[i].ip_addr == ip_addr)
Perhaps using the nginx Red-Black tree here would le
expires-1;
Does not create an "Expires: -1" header.
It should create:
Expires: Thu, 01 Jan 1970 00:00:00 GMT
A time in the “Expires” field is computed as a sum of the current time and
time specified in the directive. If the modified parameter is used (0.7.0,
0.6.32) then time is computed
>> the "error_log" and "access_log" directives now support logging to
syslog.
Is this referring to the Open Source edition? It looks to be so. I hope so
:)
On Tue, May 27, 2014 at 11:59 PM, Maxim Dounin wrote:
> details: http://hg.nginx.org/nginx/rev/0351a6d89c3d
> branches:
> changeset: 571
, Paulo Silva wrote:
> On Mon, May 26, 2014 at 9:28 AM, SplitIce wrote:
> > Yes, connecting with SOCK_NONBLOCK shouldnt block. I don't believe this
> is
> > mentioned previously. If your code blocks (e.g blocking connect or
> blocking
> > send) then it would reduc
stead
(less of a hack).
Regards,
Mathew
On Mon, May 26, 2014 at 6:18 PM, Paulo Silva wrote:
> On Mon, May 26, 2014 at 9:09 AM, SplitIce wrote:
> > As in blocking send and connect? I don't know the specifics of Unix
> Sockets,
> > but don't they block when the bu
As in blocking send and connect? I don't know the specifics of Unix
Sockets, but don't they block when the buffer fills (I know FIFO queues do)?
On Mon, May 26, 2014 at 9:22 AM, Paulo Silva wrote:
> Hi,
> I'm not sure whether I will face problems with other filters modifying
> the response body
there is room for gains here yet, was mainly curious
if thought had been placed in this area (e.g existing patches) for testing
prior to a thorough investigation.
Thanks,
Mathew
On Thu, Mar 13, 2014 at 8:08 PM, Igor Sysoev wrote:
> On Mar 13, 2014, at 12:43 , SplitIce wrote:
>
> I
provide a
performance increase in our use case.
On Thu, Mar 13, 2014 at 7:10 PM, Igor Sysoev wrote:
> On Mar 13, 2014, at 11:09 , SplitIce wrote:
>
> Has anyone put any thought into the possibility of a $binary_server_addr
> variable?
>
> Sometimes its quite useful to limit
Has anyone put any thought into the possibility of a $binary_server_addr
variable?
Sometimes its quite useful to limit certain events by server_addr instead
of the client address (e.g to limit requests made by certain UA's or other
events).
___
nginx-dev
path style).
On Mon, Dec 9, 2013 at 8:59 PM, Ruslan Ermilov wrote:
> On Sat, Nov 23, 2013 at 12:15:28PM +1030, SplitIce wrote:
> > Attached is the patch,
> >
> > This is the first time I have created a variable or really done anything
> > inside the http request proce
Yes that seems much better than taking over the u->headers_in.content_length_n
field.
Didn't realize just how similar memcache was :)
Thanks.
On Thu, Nov 28, 2013 at 8:10 PM, Maxim Dounin wrote:
> Hello!
>
> On Thu, Nov 28, 2013 at 07:39:32PM +1030, SplitIce wrote:
>
>
I have done something I shoudnt etc so as to
improve my nginx knowledge.
The commits -
https://github.com/splitice/ngx_http_redis/commit/88d423c17a8614b29635994839649c3e0d576641
https://github.com/splitice/ngx_http_redis/commit/c7dbe9fa75001787bd6602c4029e0e314798a37d
I always find myself worried
map $upstream_connecting $test {
~^93\.184\.216\.119\: 192.168.2.40;
~^192\.168\.2\.([0-9]+)\: 192.168.2.40;
}
proxy_bind $test;
Regards,
Mathew
On Sat, Nov 23, 2013 at 12:10 AM, SplitIce wrote:
> Ruslan, its funny you should mention this, I am testing a patch to do just
> th
:56 PM, Ruslan Ermilov wrote:
> On Tue, Nov 19, 2013 at 09:09:34PM +1030, SplitIce wrote:
> > An IPv6 based fallback is not the only solution we want to support,
> > ultimately we would like to be able to load-balance between them as well.
> > An error_page based solu
2013 at 10:24:43PM +1030, SplitIce wrote:
>
> > Hi,
> >
> > We use proxy_bind to ensure traffic always goes out via the same address
> as
> > the incoming request i.e the bound address where a server has many
> > addresses. This is a hard restriction in our use cas
;
}
become very common in the near future with the increased adoption of IPv6.
We have already had several requests for such functionality in the past
year.
Regards,
Mathew
On Mon, Nov 18, 2013 at 10:15 PM, Maxim Dounin wrote:
> Hello!
>
> On Sat, Nov 16, 2013 at 11:04:20PM +1030, Split
Looking at the documentation it seems there is no way to specify a proxy
bind address for both IPv4 and IPv6.
You can specify one or the other, but never both. This is a particular
issue when a configuration is setup to allow for a failure in IPv6 transit
/ routing.
Is it possible to get a proxy_
ches I was reading.
Thanks,
Mathew
On Sat, Sep 28, 2013 at 9:04 PM, Maxim Dounin wrote:
> Hello!
>
> On Sat, Sep 28, 2013 at 01:37:09AM +0930, SplitIce wrote:
>
> > I know this patch was made for 1.5.x however I patched our 1.4.x build
> > (internal modules are in the p
I know this patch was made for 1.5.x however I patched our 1.4.x build
(internal modules are in the process of being upgraded currently). However
I am still getting 000 in the logs. I am currently crawling the change logs
for similar patches.
Any chance you can remember any similar issue being res
requests for 170 seconds ?!?! to wait for file to be downloaded.
> Also all requests will be send to the origin and your proxy will generate 1
> TB traffic instead of 1 GB.
>
> It will be amazing if this feature will be implemented as a part of the
> common caching mechanism.
&g
This is an interesting idea, while I don't see it being all that useful for
most applications there are some that could really benefit (large file
proxying first comes to mind). If it could be achieved without introducing
too much of a CPU overhead in keeping track of the requests & available
parts
I agree, I view dead code at run-time as a liability. Something that can go
wrong. At compile time, you know everything about the sytem, the config
script makes assumptions and the binaries shouldnt work if moved to a
different OS etc anyway.
I am not a nginx developer just a C++ developer.
On M
Would it be possible to get a feature added to this module?
What I would like is a variable containing the name of the zone of the rule
that is responsible for the 503 error. Would be great for where there are
limits on many factors.
___
nginx-devel mail
On a side note, a good feature for nginx would be a small SHM zone for
storing SSL certificates cross reload (paired with a filemtime value) to
speed up reloads.
I run alot of SSL certificates myself (not using SNI but unique IPs) around
300 per node (and 7 nodes refreshed up to every minute) and
Ive been working on my first nginx module (well more specifically, a fork
of an existing module with permission).
Pretty close to done however found one thing thats lacking in the nginx
core (as far as I can tell). UDP Listening.
There is support for UDP sockets, so sending of UDP data is fine. H
Found a segfault in the ngx_http_syslog module.
I dont have the contact details for any of the ngsru team that developed it
so I am posting it in the mailing list in the hope a few are members.
Occurs when error_page is used, tested on a 504 error with config similar to
@e504 {
proxy_pass ...;
}
43 matches
Mail list logo
