mORMot Open Source

It seems that we don't necessarily need to specify TRestStorageExternal. The MainEngineList can completely perform external table statement queries.

the error is :
   TSqlDBOleDBConnection:OleDB error [](0x80040E14)- (line 1):'hzpy' is not a recognized built-in function name. in file 'mormot.db.sql.oledb.pas' at line 1894:

TEmploy：ID（map to External empid):integer;code,name:RawUtf8;
TTrader: ID(map to external traderId):Integer;code,name,phone:RawUtf8;

My RestServer class uses TRestServerDb. External database:mssql 2012,
I used sql: select rowid as Id,code,name,hzpy(name) as helpcode from employ.
The custom function I created on the built-in SQLite database: Db.RegisterSQLFunction(hzpyfunc,1,'hzpy');

Thank you very much. It worked. This is the first time I have used TLS in MORMOT.
  Finally, it was discovered that the problem was actually RootRedirectToUri. The third parameter was set to false by default, so it never redirected to the address of the static web page.

Thank you for your reply.
The same certificate file (in our mormot2 server, it was converted from pem to pfx using openssl), after using nginx, the browser can access normally, but there will be an insecure warning.  However, when using our mormot2 server, the browser keeps showing a 400 error: 400 Bad Request.

In order to initialize the global variable: AuthAdminDefaultPassword, set the initial password before calling the createMissingTable function.

perfect！Thank you for your work.

mormot2test compile error：

Compile Project, Mode: default, Target: D:\fpcupdeluxe_32T\ccr\mORMot2\test\fpc\bin\i386-win32\mormot2tests.exe: Exit code 1, Errors: 1, Warnings: 1
Verbose: Free Pascal Compiler version 3.3.1-17444-g490c431bf9 [2025/02/12] for i386
Verbose: Copyright (c) 1993-2025 by Florian Klaempfl and others
Verbose: Target OS: Win32 for i386
Verbose: Compiling mormot2tests.dpr
Verbose: Compiling .\test.soa.network.pas
Verbose: Compiling .\test.core.data.pas
Verbose: PPU Loading D:\fpcupdeluxe_32T\ccr\mORMot2\packages\lazarus\lib\i386-win32\mormot.net.dns.ppu
Verbose: PPU Source: mormot.net.dns.pas not found
Verbose: PPU Source: ..\mormot.defines.inc not available
Warning: Recompiling mormot.net.dns, checksum changed for D:\fpcupdeluxe_32T\ccr\mORMot2\packages\lazarus\lib\i386-win32\mormot.net.sock.ppu
Fatal: Can't find unit mormot.net.dns used by mormot.net.ldap
Verbose: Compilation aborted

For example, if the certificate expired yesterday (cc.GetNotAfter), your code: Expired := NowUtc-fRenewBeforeEndDays; expired is one month ago, cc.getNotAfter<expired is not valid.

In TAcmeLetsEncrypt checkCertificates procedure(line 1110), check the expiration date of error code:
  cc. GetNotAfter < expired
should be:
cc.getNotAfter-fRenewBeforeEndDays < NowUtc

Several global variables are defined in the mormot.rest.core unit：AuthAdminDefaultPassword，AuthSupervisorDefaultPassword，AuthUserDefaultPassword。You can set the initial password, and then change the password through the server code

By customizing the Routing class, I changed the format of the returned data to meet my requirements in the web client, but if the same interface needs to work in the pascal client, it should not be recognized correctly. Should there also be a corresponding method in the TRestClientRouting's inheritance class that can customize the data returned by parsing?

Sorry, my mistake, my json file format is corrupted.

不行，我看了返回值的16进制数字，原始字符串：out测试，  返回的16进制表示：6F7574 C3A6C2B5C28B C3A8C2AFC295，正确的UTF8编码：6F7574 E6B58B E8AF95

After many attempts, the ssl_password_file parameter does the job, but strangely, the file name specified after this parameter must be in the standard windows path, and the certificate file specified path must replace the '\' in the path with '//'.

After the test, you cannot set the password when applying for a certificate. After the password is set, the https service cannot run. After removing the password and re-applying for a certificate, it can run normally

I use nginx, the Settings are as follows, but https is not accessible,, I don't know what the problem is

server {
        listen       443 ssl;
        server_name  xxx.xx.com;
        ssl_certificate      d://sslkeystore//xxx.xx.com.crt.pem;
        ssl_certificate_key  d://sslkeystore//xxx.xx.com.key.pem;

        ssl_session_cache    shared:SSL:1m;
        ssl_session_timeout  5m;

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;
        ssl_ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH;
       

        location / {
            proxy_pass   http://127.0.0.1:81;
            proxy_redirect     default;
            proxy_set_header   Host             $host;
            proxy_set_header   X-Real-IP        $remote_addr;
            proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;
            proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
            proxy_max_temp_file_size 0;
            proxy_connect_timeout      180;
            proxy_send_timeout         180;
            proxy_read_timeout         180;
            proxy_buffer_size          4k;
            proxy_buffers              4 32k;
            proxy_busy_buffers_size    64k;
            proxy_temp_file_write_size 64k;
        }
    }

Thanks
this issue has been solved,
but this mormot.net.acme has found a new issue here, I have submitted a new topic

I trace that in asm code, the comparison of the first 4 bytes is already inconsistent