Hello!
On Tue, Sep 18, 2018 at 08:12:20AM -0400, Thomas Ward wrote:
> Downstream in Ubuntu, it has been proposed to demote pcre3 and
> use pcre2 instead as it is newer.
> https://trac.nginx.org/nginx/ticket/720 shows it was marked 4
> years ago that NGINX does not support pcre2. Are there any
> plans to use pcre2 instead of pcre3?
There are no immediate plans.
When we last checked, there were no problems with PCRE, but PCRE2
wasn't available in most distributions we support, making the
switch mostly meaningless.
Also, it looks like PCRE2 is still not supported even by Exim,
which is the parent project of PCRE and PCRE2:
https://bugs.exim.org/show_bug.cgi?id=1878
As such, adding PCRE2 support to nginx looks premature.
--
Maxim Dounin
http://mdounin.ru/
Hello,
I believe the documentation for the limit_req_zone directive on this page
is wrong:
http://nginx.org/en/docs/http/ngx_http_limit_req_module.html
It says that a rate parameter is not optional, but it is. The directive
requires at least three parameters, but
limit_req_zone $binary_remote_addr zone=limit:64k sync;
or
limit_req_zone $binary_remote_addr zone=limit:64k zone=limit:64k;
are valid, omitting the rate. I see in the code that the default is 1r/s.
Perhaps updating the documentation to list the default would be good, or
changing the code to have the rate be required.
Thank you,
Aidan Carson
# HG changeset patch
# User Marin Stavrev
# Date 1579526641 -7200
# Mon Jan 20 15:24:01 2020 +0200
# Node ID bf238762fdaf03383c2f3c3718c401e6141e3935
# Parent 6439ef81e37dfccfc3a8c57fed278bf56014ef39
Fix for the HT on request headers problem (#1752)
When client send HTTP request with a header of Content-Length that starts with
horizontal tab character (HT=0x09), Nginx responds with HTTP 400 Bad Request.
According to HTTP RFC2616 section 4.2, "... The field value MAY be preceded by
any amount of LWS, though a single SP is preferred.". The difinition of LWS is:
LWS = [CRLF] 1*( SP | HT )
So a header such as the following should be processed fine:
Content-Length:<0x09>110\r\n
diff -r 6439ef81e37d -r bf238762fdaf src/http/ngx_http_parse.c
--- a/src/http/ngx_http_parse.c Fri Jan 17 12:13:02 2020 +0300
+++ b/src/http/ngx_http_parse.c Mon Jan 20 15:24:01 2020 +0200
@@ -1000,6 +1000,7 @@
case sw_space_before_value:
switch (ch) {
case ' ':
+ case '\x9':
break;
case CR:
r->header_start = p;
@@ -1023,6 +1024,7 @@
case sw_value:
switch (ch) {
case ' ':
+ case '\x9':
r->header_end = p;
state = sw_space_after_value;
break;
@@ -1042,6 +1044,7 @@
case sw_space_after_value:
switch (ch) {
case ' ':
+ case '\x9':
break;
case CR:
state = sw_almost_done;
The "How to report bug" page at trac.nginx.org says:
"You need to authorize with Google, GitHub, StackExchange or Yandex to
submit bug report."
I have logged in to Trac with my GitHub account. I am seeing "logged
in as Val Kulkov" in the top line of the page. But there is no way to
submit a bug report! There is no button, no link, nothing. I can only
see reports, but I cannot open a new ticket.
Is there some problem with the Trac server [again]? Can someone check
what is going on please? Thanks.
Hi,
I would like to know if njs supports regex positive look behinds.
I have written a script in perl and would like to convert it to njs. The
reg ex I have in perl is
"((?<=[a-z])(?=[A-Z])(?!ID)(?!^Open$)|(?<=ABC)|(?<=API)(?=[A-Z])|(?=Connect))"
This would give the following outputs.
*Inputs and expected outputs* are *listed below* in the format *Input ->
Expected Output*
1.
InstallAndSetup -> install-and-setup
2.
DeployingABCDefGhijk -> deploying-abc-def-ghijk (assuming abc is a noun
that is frequently used)
3. OpenIDConnect -> openid-connect
4. OAuth2Scopes->oauth2-scopes
5. APISecurity -> api-security
I would like to know if there's a way to achieve this with njs?
Thank you in advance.
Regards,
Shani.
Hello Nginx developers,
I was not able to find any information what continous integration (CI)
Nginx project is using.
I'd like to ask whether you run a CI server/agent on ARM 32/64 architecture
?
At my job we are going to use more and more ARM64 based servers and we
would like to know whether this is a safe bet with Nginx.
At https://nginx.org/en/index.html
<https://nginx.org/en/index.html#tested_os_and_platforms>#tested_os_and_platforms
I see " Linux 3 — 4 / armv6l, armv7l, aarch64, ppc64le;". Does that mean
that Linux 5.x is not supported/tested or just that this documentation page
needs to be updated ?
Thank you!
Regards,
Martin Grigorov