>>
>> If it helps, I'm using bramus router and my configured paths are as
>> follows :
>>
>
> Looks like the logic for getting base path is a bit interesting. Try
> this for related line:
>
> fastcgi_param SCRIPT_NAME /demo/;
>
That didn't work unfortunatley.
Just dug up their code and I see wh
Hi
On Thu, Jun 16, 2016, at 22:06, Ben wrote:
>
> >>
> >> If it helps, I'm using bramus router and my configured paths are as
> >> follows :
> >>
> >
> > Looks like the logic for getting base path is a bit interesting. Try
> > this for related line:
> >
> > fastcgi_param SCRIPT_NAME /dem
Hi
On Thu, Jun 16, 2016, at 22:11, Edho Arief wrote:
> >
> > for /demo/ it prints "/demo/"
> > and
> > for /demo/hello/x it prints "/demo/hello"
> >
> > Which looks like their "auto base-path" is setting moving goalposts !!
> >
>
> That doesn't make sense if you actually use my configuration s
On 16/06/2016 14:14, Edho Arief wrote:
Hi
On Thu, Jun 16, 2016, at 22:11, Edho Arief wrote:
for /demo/ it prints "/demo/"
and
for /demo/hello/x it prints "/demo/hello"
Which looks like their "auto base-path" is setting moving goalposts !!
That doesn't make sense if you actually use my co
If the external server that I'm getting the data from doesn't have a
relational database (and instead responds to udp requests), will I still be
able to cache multiple fields from one udp request using Lua so that I can
access them in the conf file later? Can you clarify what you mean by Lua
cache?
Are there any plans to move from pcre (8.x) to pcre2 (10.x)? I realize that
the API changed quite a bit but it would be awesome if there was a migration
plan for it.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265726,267649#msg-267649
___
Theoretically yes, it all depends how and by what means this data is
collected and if you need to wait for some parts, have a look at the example
Urls I send before or join the openresty forum on googlegroups with some
example code/description what your after.
nb. a Lua cache is an in-memory cache
Hello, I have created my own NGINX module, which get rest request and return
a response.
When I send a response with status 500 (NGX_HTTP_INTERNAL_SERVER_ERROR) or
404 (NGX_HTTP_BAD_REQUEST) I see on the memory uses that the nginx processes
is growing up
PID USER PR NIVIRTRESSH
Hello!
On Thu, Jun 16, 2016 at 10:25:28AM -0400, gitl wrote:
> Are there any plans to move from pcre (8.x) to pcre2 (10.x)? I realize that
> the API changed quite a bit but it would be awesome if there was a migration
> plan for it.
As of now there are no plans, but we are keeping eye on it. Th
This is a general remark, adding stuff to handle a bad request, ea., will
eventually kill the performance, sending bad requests is a popular way to
create a DOS/DDOS attack since the server(the added module) has to process
them and do something while technically it makes no sense to do anything at
I will definitely join the google group and check out Lua. Thanks for your
help!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267611,267654#msg-267654
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
As some might have noticed, the expiration date of the GPG key we use to
sign repos and packages for Linux distributions [1] was getting close
(2016-08-17), so I've prolonged the key validity until 2024-06-14. The
ID of the key stays the same.
If you're using Debian/Ubuntu packages from n
12 matches
Mail list logo
