CppCMS 0.999.1 - Release Candidate 2
All CppCMS 1.0.0 milestone tasks had completed and thus the second release candidate was released. It contains mostly bug fixes including several security bug fixes. It is expected to be the last RC before the stable version would be delivered.
All CppCMS users please download the RC2 and test it. If no critical problems would be found the stable version would be announced in a week or two.
Whats New?
Security Bug Fixes:
- Fixed a bug when calling
reset_session()
would not reset it when session content itself was not changed. - Fixed a bug that could cause infinite waiting when POST data contained incomplete multi-part data potentially causing DOS.
Breaking Changes:
The protocol between cppcms_scale
and cppcms
clients had changed,
you can't use old cppcms_scale
with newer versions of cppcms
and vise versa.
The protocol now uses absolute 64 bit time-stamp rather then relative one.
New Features:
- Many new unit tests implemented giving good test coverage for the CppCMS framework.
- Added support of nginx with SCGI protocol to
cppcms_run
- Many examples added: Asynchronous I/O, Serialization, Templates Inheritance. Some examples updated to use moder API.
Bug Fixes:
- Fixed a bug that prevented "Keep-Alive" option to work with FastCGI protocol.
- Session cookie was not delete on clear session call with server side session storage.
- Fixed a bug that caused a session value to be unexposed what it was updated.
- Fixed incorrect call of
view_builder
instead ofunsafe_view_builder
when unsefe option was given - Fixed status handling according to HTTP/CGI specifications in case of invalid POST input.
- Fixed a bug when in certain situations sockets were not shutdown properly.
- Added better error reporting when the content of invalid type was used during view rendering.
- Fixed
cppcms_run
to setup nginx'sPATH_INFO
correctly according to the options available in the latest version.
Comments
Cool! Thanks for the great work!
Im very glad. Fast support, fast devel. Thank you very much
Add Comment:
You must enable JavaScript in order to post comments.