Jexus 5.8.2 is officially released to provide platform support for ASP into the production environment

The Jexus is a WEB server and reverse proxy server that runs on the Linux platform and features a high security and high performance feature in support of ASP. The latest version of 5.8.2 has been released with the following updates:

1, now most of the site has been deployed HTTPS, we are more and more attention to security, comply with the trend of new HTTPS multi-certificate support, each site can configure their own independent SSL certificate, there are 2 ways to support the site deployment of HTTPS.

A, add SSL configuration used by the whole server: if required, you can add an SSL configuration to provide sharing for all sites that do not have SSL configured separately, this configuration provides the convenience of supporting a generic domain name certificate.
By modifying the "Certificatefile" and "Certificatekeyfile" entries in jws.conf, fill in the certificate file and the private key file (absolute path) separately.
B. Add SSL configuration for the specified Web site: The method is to modify the site configuration file to fill in the certificate file and the private key file (absolute path) for "Ssl.certificate" and "Ssl.certificatekey" entries, respectively.
Note 1: Site enable Https,port must be set to 443, and the value of Usehttps is set to true.
Note 2:jexus HTTPS requires a function library named Libssl support, if your server does not have libss.so.xxx files, you need to install OpenSSL.
For the general version, register the LIBSSL with/usr/etc/mono/config to add a line to the file (assuming that the LIBSSL filename is "libssl.so.1.0.0"):
"<dllmap dll=" Libssl "target="/lib/x86_64-linux-gnu/libssl.so.1.0.0 "/>"
For stand-alone versions, simply connect the Libssl to the Jexus Runtime/lib folder, such as:
"Sudo ln-s//lib/x86_64-linux-gnu/libssl.so.1.0.0/usr/jexus/runtime/lib/libssl.so"

Note 3: If you have a separate SSL certificate for the site, the hosts entry for that station will need to match the domain name supported by the SSL certificate.

2, new Apphost (HTTP self-hosted application Manager) configuration item for managing and high-speed data forwarding of self-hosted applications such as ASP. NET Core, node. js, Tomcat, and provide synchronous management and high availability consistent with site operations for self-hosted service programs Provides multi-port support for Apphost.port (application port forwarding).

3, enable the Keep connection multiplexing mechanism of fastcgi, and further improve the performance of data exchange between fast CGI handlers such as PHP.

4, perfect the Close method of WebSockets.

6, added support for HTTP patch method.

7, fixed when using HTTPS to fastcgi, reverse proxy post data, there may be incomplete data bugs.

8, the static file concurrency processing speed increased by about 14%.

The highlight of this release is the addition of a "AppHost" configuration item that incorporates HTTP self-hosted applications (such as ASP. JS applications, etc.) into the Jexus process sequence for control (start, stop, restart, auto-resume after crash, etc.) Provides a strong platform for ASP. NET core applications into the enterprise production environment. The advantages of using Jexus to consolidate ASP. NET Core:

1) Support multi-site, the same port can support any number of ASP.
2) application start, stop, restart and site start, stop, restart and other operations consistent, no need to manually manage the ASP.
3) with application crash after automatic restart function, for enterprise-class uninterrupted operation protection;
4) has a higher performance advantage than the reverse proxy.

5) Provide the same HTTP environment parameters as IIS.

The configuration format for Apphost is:
apphost={cmdline= application command line; approot= Application working directory; port= application HTTP Listening port}, where:
"CmdLine" means the command line that launches the application, such as: Dotnet/var/www/site1/app.dll;
"AppRoot" indicates the application working directory, such as:/var/www/site1;
"Port" indicates the listening port used by this HTTP application, such as: Asp.core (the default port is 5000).

For example, suppose that the path to the ASP. NET core application is "/var/www/mysite", its launcher is in the 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}

Below we present an example of the CentOS configuration ASP. core+ Jexus Runtime Environment

Install. NET core 1.1 with visual Studio Update 3 and create an ASP. My code is placed in the https://github.com/geffzhang/AspNetCoreStarted

Installing the jexus5.8.2 standalone version

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= working path; port= Port Number}
Description: CmdLine: Required option. Indicates the command (with parameters) to start the Web application, such as Cmdline=/var/www/mysite/webapp
AppRoot: Required option. Represents the working directory for this application, such as: Approot=/var/www/mysite
Port: Optional. Represents the listening port for this application, with multiple ports separated by commas (note: If this is not the case, please fill in the port number in Apphost.port or reproxy, otherwise the request data cannot be forwarded to the application).
ENV: Optional parameter. Represents the environment variables that are required for this application to work, such as env= (Path=/myhost/bin: $PATH), with multiple settings separated by commas.
ErrLog: Options available. Indicates that the exception output of this application is redirected to the specified file (full path required);
Outlog: Options available. Indicates that the console output of this application is redirected to the specified file (full path required);
User: Available options. Runs the application as the specified user, which is the default root identity.
Attention:
1,apphost like Apphost.port, virtual paths are not supported;
The 2,apphost feature is the ability to manage a specified Web application with HTTP service capabilities into a Jexus worker process, which is important for self-hosted web programs such as ASP. NET Core or node. js for production environments.

Try before the Jexus takes over to ensure that the application is running properly on the server

Start the management of the Jexus service takeover application

Cd/usr/jexus

./jws Start

Visit our website in a browser:

Jexus 5.8.2 is officially released to provide platform support for ASP into the production environment