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:
As such, adding PCRE2 support to nginx looks premature.
Dear NGINX developers,
we are using C++ dynamic modules in our NGINX based servers, while multiple Debian distributions have to be supported.
On older Debian distributions it is impossible to use more recent C++ standard, due to build defaulting to system provided clang package.
Our developers stood before decision to either create wrappers around modern C++ libraries which would be compliant with older standards or write the entire logic using obsolete featureless language.
Neither of these approaches is sustainable in terms of developers' productivity and long term maintenance.
Would it be possible to consider a change in dynamic modules' build system, so that C++ flags may be provided?
We propose a low intrusive changes concerning 3 files. The changes are backwards compatible: if CXX is not provided by an user, the build uses CC instead (as well as CFLAGS instead of CXXFLAGS).
Would you be so kind and share your opinion on those? Please find attachment provided bellow (the patch was created using Quilt).
Je dobré vědět, že tento e-mail a přílohy jsou důvěrné. Pokud spolu jednáme o uzavření obchodu, vyhrazujeme si právo naše jednání kdykoli ukončit. Pro fanoušky právní mluvy - vylučujeme tím ustanovení občanského zákoníku o předsmluvní odpovědnosti. Pravidla o tom, kdo u nás a jak vystupuje za společnost a kdo může co a jak podepsat naleznete zde<https://onas.seznam.cz/cz/podpisovy-rad-cz.html>
You should know that this e-mail and its attachments are confidential. If we are negotiating on the conclusion of a transaction, we reserve the right to terminate the negotiations at any time. For fans of legalese—we hereby exclude the provisions of the Civil Code on pre-contractual liability. The rules about who and how may act for the company and what are the signing procedures can be found here<https://onas.seznam.cz/cz/podpisovy-rad-cz.html>.
user: Maxim Dounin <mdounin(a)mdounin.ru>
date: Fri Feb 28 17:21:18 2020 +0300
Added default overwrite in error_page 494.
We used to have default error_page overwrite for 495, 496, and 497, so
a configuration like
error_page 495 /error;
will result in error 400, much like without any error_page configured.
The 494 status code was introduced later (in 3848:de59ad6bf557, nginx 0.9.4),
and relevant changes to ngx_http_core_error_page() were missed, resulting
in inconsistent behaviour of "error_page 494" - with error_page configured
it results in 494 being returned instead of 400.
Reported by Frank Liu,
src/http/ngx_http_core_module.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diffs (11 lines):
diff -r f47f7d3d1bfa -r f001d9384293 src/http/ngx_http_core_module.c
--- a/src/http/ngx_http_core_module.c Wed Feb 26 15:10:46 2020 +0300
+++ b/src/http/ngx_http_core_module.c Fri Feb 28 17:21:18 2020 +0300
@@ -4687,6 +4687,7 @@ ngx_http_core_error_page(ngx_conf_t *cf,
+ case NGX_HTTP_REQUEST_HEADER_TOO_LARGE:
err->overwrite = NGX_HTTP_BAD_REQUEST;
Trying to make nginx work as SMTP server and/or SMTP proxy. Done everything according to:
But excluded (don't care about SSL at this point so don't want to install/configure Perl now):
nmake was successful and nginx.exe was created.
However nginx.exe keeps failing with the error:
WSASend() failed (10057: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied) while in http auth state, client: 127.0.0.1, server: 0.0.0.0:8025
Windows API says the following about this error:
Socket is not connected.
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto<https://docs.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-sen…>) no address was supplied. Any other type of operation might also return this error—for example, setsockopt<https://docs.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-set…> setting SO_KEEPALIVE<https://docs.microsoft.com/en-us/windows/desktop/winsock/so-keepalive> if the connection has been reset.
Windows Sockets Error Codes (Winsock2.h) - Win32 apps | Microsoft Docs<https://docs.microsoft.com/en-us/windows/win32/winsock/windows-sockets-erro…>
Return code/value Description; WSA_INVALID_HANDLE 6: Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid.
Managed to debug your code in VS 2010 a little bit but it's brutal C so it's hard to figure your code out. And this debugger doesn't show you any local variables values.
Any recommendation for me to make it work?
Tried to play with config (commenting/uncommenting):
#error_log logs/error.log notice;
#error_log logs/error.log info;
# auth_http none;
# smtp_auth login plain cram-md5;
# smtp_capabilities "SIZE 10485760" ENHANCEDSTATUSCODES 8BITMIME DSN;
Tried both under a regular user and under admin. Tried on 25, 1025 and 8025 ports.