v2.1.1- Session Authentication fixed

Session authentication would not work in certain (probably most) environments since there was an sql error

Full Changelog: v2.1.0...v2.1.1

v2.1.0 - Session Authentication re-added

Session Authentication is possible again.

• Requests can now be authenticated by using the user and session header and providing appropriate values in each header.
• Sessions can now be created by using the /session/auth endpoint
• Sessions can be extended by using the /session/extend endpoint
• Sessions are automatically extended when successfully authenticating against any endpoint using a session token

Full Changelog: v2.0.0...v2.1.0

v2.0.0 - Changed Partial XML Syntax

Partial Documents had no Root node (which is invalid in standard XML), therefore the structure of the partial document was changed.

The Structure of the Full Document was not changed, therefore Clients need only adjustments when handling partial documents.
Refer to the wiki for details on the current structure

Full Changelog: v1.1.0...v2.0.0

v1.1.0 - Checksums

Added a new Endpoint called 'checksum' which returns the calculated checksum of your document in plain text

Full Changelog: v1.0.0...v1.1.0

v1.0.0 - Changed Authentication

User have user ID's now.
This requires changes to existing SQL databases!
Users can now choose to authenticate either with the api-token or their user password.

Session authentication is now disabled and will be changed with the next release

v0.3.0 - Content Filtering

Mainly you can now Filter the main document to just show entries and directories which contain a specific (sub) node (optionally with a specific value). This ability leads to new endpoints with which you can filter either manually for contained sub-nodes, or use other helpers in context with due and priority properties. Here is a list of all new endpoints:

• /xml/priority/highest To get only the nodes which have the highest priority among the document
• /xml/priority/{priority} To get only nodes which priority is higher (lower numerical value) or equal to the provided priority.
• /xml/filter/{name}/{value} To only get nodes which have subnodes called NAME whose value equals VALUE (not case sensitive)
• /xml/due/over To get only nodes wich were due in the past.
• /xml/due/today To get only nodes wich are due or on today.
• /xml/due/tomorrow To get only nodes which are due or on tomorrow.
• /xml/due/in/{start}/{end} To get only nodes which due date is in between start and end

Release v0.2.0

• New Endpoint: get_by_id
• Removed Version number from the endpoint URI (if you still require the v1 I would suggest to do so in the proxy configuration)
• Improved XML validation

Release v0.1.0 - First Release

First functioning Release

The following endpoints are available:
/v1/xml/fetch
/v1/xml/update
/v1/xml/validate