Shulou(Shulou.com)06/02 Report--

Jexus is a WEB server and reverse proxy server that runs on Linux platform and supports ASP.NET and PHP, which integrates high security and high performance. The latest version 5.8.2 has been released with the following updates:

1. Now most websites have deployed HTTPS, and we are paying more and more attention to security. In line with the trend, we have added HTTPS multi-certificate support. Each website can configure its own independent SSL certificate. Now there are two ways to support website deployment of HTTPS.

A. add a server-wide SSL configuration: if necessary, you can add a ssl configuration to provide sharing for all websites that do not have a separate configuration of ssl. This configuration provides convenience for certificates that support pan-domain names.

By modifying the "CertificateFile" and "CertificateKeyFile" entries in jws.conf, fill in the certificate file and the private key file (absolute path), respectively.

B. Add SSL configuration for the specified website: modify the website configuration file by filling in the certificate file and private key file (absolute path) for "ssl.certificate" and "ssl.certificatekey" entries, respectively.

Note 1: Web site https,port must be set to 443.The value of UseHttps must be set to true.

Note 2:Jexus Https needs to be supported by a library called libssl. If your server does not have libss.so.xxx files, you need to install openssl.

For the general version, register libssl with / usr/etc/mono/config, adding a line to the file (assuming the file name of libssl is "libssl.so.1.0.0"):

"

For standalone versions, you only need to connect the libssl software to the runtime/lib folder of jexus, such as:

"sudo ln-s / / lib/x86_64-linux-gnu/libssl.so.1.0.0 / usr/jexus/runtime/lib/libssl.so"

Note 3: if the website is equipped with a SSL certificate alone, the domain name entered in the hosts entry of the site must be the same as the domain name supported by the SSL certificate.

2. A new AppHost (HTTP homing Application Manager) configuration item is added, which is used for the management and high-speed data forwarding of Asp.net Core, Node.js, Tomcat and other self-hosting applications, providing synchronous management and high availability consistent with site operations for self-hosting service programs, and multi-port support for AppHost.Port (Application Port forwarding).

3. Enable the KEEP connection reuse mechanism of FastCGI to further improve the performance of data exchange with FastCGI processors such as PHP.

4. Perfect the Close method of WebSockets.

6. Add support for HTTP PATCH method.

7. Fix the possibility of BUG with incomplete data when using Https to fastcgi and reverse proxy POST data.

8. The concurrent processing speed of static files is increased by about 14%.

The highlight of this edition is the new "AppHost" configuration item, which integrates HTTP self-hosting applications (such as Asp.net Core applications, Node.js applications, etc.) into the working process sequence of Jexus for management and monitoring functions (such as start, stop, restart, automatic recovery after crash, etc.), thus providing a strong platform guarantee for Asp.Net Core applications to enter the enterprise production environment. Advantages of using jexus to integrate asp.net core:

1) support multiple sites, and support any number of asp.net core applications on the same port at the same time

2) the start, stop and restart of the application are consistent with the start, stop and restart of the site, and there is no need to manage the asp.net core application manually

3) it has the function of automatic restart after the application crashes, which ensures the enterprise-level uninterrupted operation.

4) it has higher performance advantage than reverse proxy.

5) provide the same HTTP environment parameters as IIS.

The configuration format of AppHost is:

AppHost= {CmdLine= application command line; AppRoot= application working directory; Port= application HTTP listening port}, where:

"CmdLine" represents the command line that starts the application, such as dotnet / var/www/site1/app.dll

"AppRoot" indicates the working directory of the application, such as / var/www/site1

"Port" indicates the listening port used by this HTTP application, such as 5000 (the default port for Asp.Core is 5000).

For example, if the path to the Asp.Net Core application is "/ var/www/mysite", the startup program is stored in this folder, the name is "webapp", and the listening port after the program starts is 5000, then the AppHost configuration should be:

AppHost= {CmdLine=/var/www/mysite/webapp;AppRoot=/var/www/mysite; port=5000}

Let's give an example to introduce the Centos configuration ASP.Net Core+ Jexus runtime environment

Install. Net core 1.1 with Visual Studio 2015 Update 3, create an asp.net core project, and put my code in https://github.com/geffzhang/AspNetCoreStarted

Install jexus5.8.2 standalone version (recommended)

Cd / tmpwget linuxdot.net/down/jexus-5.8.2-x64.tar.gztar zxvf jexus-5.8.2-x64.tar.gzcd jexus/cd siteconf/vi default

Add AppHost

Format: AppHost= {CmdLine= life line; AppRoot= work path; Port= port number}

Description: CmdLine: required. Indicates the command (with parameters) to start the web application, such as CmdLine= dotnet / var/www/aspnetcore/AspNetCoreStarted.dll

AppRoot: required. Represents the working directory of this application, such as: AppRoot=/var/www/aspnetcore

Port: optional. Indicates the listening port of this application, with multiple ports separated by English commas (note: if you do not fill in this item, please fill in the port number in AppHost.port or reproxy, otherwise, the request data cannot be forwarded to the application).

Env: optional parameter. Indicates the environment variables needed for the application to work, such as env= (PATH=/usr/local/bin:/var/www/aspnetcore:$PATH), with multiple settings separated by English commas.

ErrLog: optional. It means to redirect the abnormal output of this application to the specified file (you need to fill in the full path). If you do not want to output the log, you can not use the OutLog entry. At this point, jexus will automatically turn off the console output (essentially redirected to / dev/null)

OutLog: optional. Indicates that the console output of this application is redirected to the specified file (full path is required)

User: optional. Run the application as the specified user, which defaults to root.

Note:

1. AppHost, like AppHost.Port, does not support virtual paths

2. The AppHost function is to bring the designated web applications with http service capabilities into the jexus work process for management, which is of great significance for self-hosting web programs such as Asp.Net Core or Node.js to be used in the production environment.

Try it before Jexus takes over to make sure the application is running properly on the server

Start jexus service to take over the management of the application

Cd / usr/jexus

. / jws start

Visit our website with a browser:

Let's check the log output in the / tmp directory:

The log we want has been generated:

OutLog outputs a lot of logs. When using the product operating environment, you should raise the log level to the err level, which will have a lot less records, and will not affect the speed, and will greatly improve the performance without generating logs. The level of logs can be set as follows:

Let's take a look at the progress of Jexus and asp.net core.

As you can see in the image above, it is indeed a child process under the monitoring of jexus.

The above is the whole content of this article, I hope it will be helpful to your study, and I also hope that you will support it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.