The second Beta is here

admin

Dear all,
The second Beta of the upcoming version 2.14 is here. It fixes the few issues reported for Beta 1.
DISCLAIMER:
This Beta release is not suitable for production environments. Use it only for test purposes. Do not distribute it. This is not the final product and it may be unstable or contain bugs.
GETTING THE NEW BETA:
Please do not use this test release if you are not familiar with Abyss Web Server.

Windows version: https://aprelium.com/data/abwsx1-2-12-5-b2.exe
Linux version: https://aprelium.com/data/abwsx1-2-12-5-b2.tgz
macOS version: https://aprelium.com/data/abwsx1-2-12-5-b2.dmg

Installation and upgrading instructions are exactly the same as those already in http://www.aprelium.com/abyssws/download.php .
NOTE TO X2 USERS:
Beta 1 is available upon request for X2 customers. Please contact our priority technical support to enable Beta access for your user account.
IMPORTANT NOTES:
When upgrading from a previous version, we recommend that you first make a backup copy of your old abyss.conf file.
The documentation shipping with the Beta is updated and documents the new additions.
This Beta release's internal version is 2.12.5. This is not a mistake. The final stable version will be numbered 2.14.
DIFFERENCES BETWEEN BETA 2 AND 1

Updated the HTTP parser to be stricter.

Changed the Keep-Alive support for HTTP requests to be conformant to the modern RFC 7230 HTTP specification.

Updated the TLS shutdown sequence for HTTPS connections.

Added a missing TLS 1.3 checkbox in the custom SSL/TLS profile defintion in the console.

CHANGES AND NEW FEATURES IN THE UPCOMING VERSION 2.14:

SSL/TLS
- Added support for TLS 1.3
- Added support ciphers based on Elliptic-curve Diffie-Hellman (ECDH) and Diffie-Hellman key Exchange (DHE)
- Exposed a parameter in custom SSL/TLS profiles declarations to honor server ciphers list order
- Updated predefined SSL/TLS profiles to account for modern browsers and TLS 1.3 introduction
- Removed support for the deprecated and insecure SSL3 protocol
ACME
- Added HTTP proxy configuration to ACME Bot
- Added support for POST-as-GET in ACME
- Added support for skipping hostname * from ACME certificate generation
Server Core
- Updated HTTP OPTIONS verb handling to fully respect the HTTP/1.1 specification
- Improved HTTP headers request and response processing to respect all the edge cases of the HTTP/1.1 specification (empty HTTP headers, folding of multiple-valued headers, special handing of Set-Cookie and Set-Cookie2 headers)
- Fixed a bug occurring with X-Sendfile when both chunked encoding and compression are active
- Updated IP address string conversion to generate easier-to-read IPv4 addresses instead of IPv4-over-IPv6 style ones
SSI
- Updated SSI processing of expressions to add support for the == comparison operator
- Fixed SSI parsing of attribute values enclosed between quotes or backticks
- Added proper regular expression parsing in SSI
Windows specific changes
- Improved Windows installer
- Updated the Windows installer to restrict access permissions to the installation directory and to the kcstore subdirectory
macOS specific changes
- Added notarization to conform to the stricter security rules of macOS Catalina 10.15
- Modernized the DMG package for macOS (added a graphical background with installation instruction)
- Deprecated old method to run privileged operations on macOS and replaced it by a proper helper tool
- Updated the Help book to be conformant to the modern macOS help specifications
Operating systems compatibility
- Changed minimum operating system requirement to Windows XP, Mac OS X 10.9 and any Linux with GLIBC 2.4
- Updated integrated documentation to adapt to dark mode on macOS and Windows 10
- Cleaned the source code base from artifacts related to legacy operating systems.

YOUR FEEDBACK IS IMPORTANT TO US:
We're eagerly waiting for any feedback from you. Please let us know how the new features worked for you.
If you're using macOS, please feel free to let us know what you think about the specific changes affecting that edition.
Please send us your bug reports and feedback to support@aprelium.com .
WE ARE HERE TO HELP:
If you experience any issue during the updating process or have any feedback, please feel free to contact priority@aprelium.com.
THANK YOU!
Thank you for supporting Abyss Web Server.

tfh

The 1st beta ran fine and stable. TLS1.3 worked fine.
Running the 2nd beta now.

admin

tfh wrote
The 1st beta ran fine and stable. TLS1.3 worked fine.
Running the 2nd beta now.

Thank you for your support and help with Beta testing Abyss Web Server. If you have any feedback, please feel free to share it with us.

Daevon

Hello
When using url rewrite rules, if a rule is to give an error (eg 500) and a custom error page for 500 is defined, the standard error page is used instead of the custom one.

admin

Daevon wrote
Hello
When using url rewrite rules, if a rule is to give an error (eg 500) and a custom error page for 500 is defined, the standard error page is used instead of the custom one.

We have already replied to your questions in https://aprelium.com/forum/viewtopic.php?p=790563#790563 . have you checked it?

Daevon

sorry, that was a double post by mistake since the forum does not publish my messages immediately as I am (by error) still marked as a new user

Daevon

Hi
Upgrading from an old install, doesn't seem the permissions of the install folder were altered.
Is this normal? Need a fresh install in order to have the custom folder permissions applied?
Thanks!

Daevon2

I did an upgrade to beta2, and even tho I have default webpage set to index.html and index.php, I was shown the Aprelium first-install index.
I had to manually delete it in order to have the Index.html I had in my www root. Even in this way, browsing from Chrome on Android, I have some time
ERR_EMPTY_RESPONSE while opening

https://examplewebsite.org

unless I do specify the index page, it

https://examplewebsite.org/index.html

admin

Daevon wrote
Hi
Upgrading from an old install, doesn't seem the permissions of the install folder were altered.
Is this normal? Need a fresh install in order to have the custom folder permissions applied?
Thanks!

The new permissions are applied only for a new setup. This is to avoid any possible issues with already running systems.
By the way, you can apply the same permissions using standard Windows properties > Security features.

admin

Daevon2 wrote
I did an upgrade to beta2, and even tho I have default webpage set to index.html and index.php, I was shown the Aprelium first-install index.
I had to manually delete it in order to have the Index.html I had in my www root. Even in this way, browsing from Chrome on Android, I have some time
ERR_EMPTY_RESPONSE while opening
https://examplewebsite.org
unless I do specify the index page, it
https://examplewebsite.org/index.html

The order of index files is important. Also your browser could be serving a stale response without even contacting the server. A hard refresh on the browser side may sometimes be required.
ERR_EMPTY_RESPONSE is another issue. It could be that the index.php script had an error and forced the server to abruptly stop the connection. It may also be a network issue.