1.0.3

Bug

• [RH-120] - request json payload might get cut leading to 406 bad request response

1.0.2

Release Notes - Restheart - Version 1.0.2

Bug

• [RH-115] - some link templates are wrong
• [RH-117] - Usin string methods to decode multibyte-encoded text from a stream can lead to character corruption

Improvement

• [RH-118] - If the request has a 'properties' part which contains a filename key then override the content disposition's filename

1.0.1

Bugfix: resolved issue https://softinstigate.atlassian.net/browse/RH-111
(Upload file service was not compatible with multipart/form-data standard)

1.0.0

Release Notes - Restheart - Version 1.0.0

Major Release

This is a major, production ready release.
Upgrading is strongly suggested.

Bug

• [RH-91] - RESTHeart integration tests fail "sometimes"
• [RH-92] - wrong result set due to eager dbcursor preallocation
• [RH-93] - wrong rels link when string id contains spaces
• [RH-102] - wrong links in embedded resource

Improvement

• [RH-90] - Improve dbs/collections scan on startup
• [RH-96] - update undertow to 1.2
• [RH-103] - improve curies mgmt and documentation

0.10.4

Bugfixes and enhancements

DELETE operation reports ETag header as required instead of If-Match which is actually checked
#41 opened 15 days ago by gokrokvertskhov

Add Keys field for Collection enhancement feature
#40 opened 15 days ago by gokrokvertskhov

0.10.3

Release Notes - Restheart - Version 0.10.3

Improvement

• lot of improvements to schema validation/enforcement via SimpleContentChecker

Bug

• [RH-81] - on update returned ETag is wrong
• several minor bug fixes

0.10.2

Release Notes - Restheart - Version 0.10.2

Bug

• [RH-35] - relations on nested document fields

Improvement

• [RH-54] - consider replacing our AccessManagerHandler with AccessControlListHandler

New Feature

• [RH-49] - DB based IDM implementation
• [RH-53] - schema validation/enforcement
• [RH-68] - automatic document transformation via collection metadata

0.10.1

Release Notes - Restheart - Version 0.10.1

Bug

• [RH-71] - GetRoleHandler does not take auth token into account
• [RH-72] - requests to /_authtoken/<userid> lead to 401 Unauthorized
• [RH-74] - wrong return code if request is not permitted but user is authenticated
• [RH-75] - CORS headers not injected on ApplicationLogicHandler if authentication fails
• [RH-76] - Auth-Token-* headers cannot be read by browser when request is to a different domain
• [RH-78] - RequestContext does not flow through Security Handlers chain

Improvement

• [RH-69] - determine file contentType automagically
• [RH-77] - simplify how AccessManager can take decisions based on request body
• [RH-80] - Insert the new Etag in the HTTP headers after a PATCH

0.10.0

this is a major update; new and notable improvements:

• strict mode representation for MongoDB extended JSON (*)
• token based authentication
• query execution optimization via the eager dbcursor preallocation engine
• support for GridFs (early release, feedbacks appreciated)
• can fork server process with --fork option (not available on windows)
• better support for data created by other clients (for instance by the mongo shell)
  • dbs and collections not created by RESTHeart are now immediately visible (no need for server restart anymore)
  • support for other doc id types (id type can be specified via the id_type query parameter)
  • collections properties moved to the reserved _properties collection (**)
  • _created_on property is not stored on documents anymore (generated from _id when it is an ObjectId)
• allowed pagesize=0 to avoid _embedded resources at all
• several bug fixes
• all code repackaged to org.restheart
• refactoring, more test cases and better code quality
• updated all dependencies (notably, undertow 1.1.2.Final)

Note: if updating from versions <= 0.9.7:

• resource representation and filter expression changed (*)
• need to move the collections properties to _properties collection (**)

0.9.7

Important bug-fix release. It is recommended to upgrade.

• 62e509b - Release 0.9.7
• d58d8bb - Fixed a CollectionDAO.getCollectionSize bug which resulted in wrong query result for successive method calls.
• 7007760 - test refactoring