Skip to content

Changes in v1.2

Introduction of rate limiting
Due to the growing number of Obelisk users, we are forced to introduce rate limiting as a means for enforcing fair use and to guarantee a certain quality of service. Check your HTTP Response Headers (X-RateLimit-*) for more information on the current state of your sessions.

Project partners who are having issues with rate limiting can post an issue using the helpdesk.

Additionally, session management for SSE streams has been introduced. Each client is allowed to have one active SSE stream per Scope. Stale sessions (e.g. while developing, a stream was not properly closed) that are preventing the creation of a new SSE stream, can be forcefully closed using the Obelisk Explorer.

Many bugfixes
The v1.1 release was a major update and lots of small issues still needed fixing.