You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+28-9Lines changed: 28 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,41 +7,59 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [Unreleased]
9
9
10
+
<!-- ### Added -->
11
+
12
+
<!-- ### Changed -->
13
+
14
+
<!-- ### Fixed -->
15
+
16
+
<!-- ### Deprecated -->
17
+
18
+
<!-- ### Removed -->
19
+
20
+
<!-- ### Security -->
21
+
22
+
<!-- ### Technical Improvements -->
23
+
24
+
## [2.3.0] - 2019-12-13
25
+
10
26
### Added
11
27
12
-
- Added longpolling as new connection type [#217](https://github.com/Accenture/reactive-interaction-gateway/issues/217)
28
+
- In addition to SSE and WebSocket, RIG now also supports HTTP long-polling for listening to events. Frontends should only use this as a fallback in situations where neither SSE nor WebSocket is supported by the network.
- When terminating an SSE connection after its associated session has been blacklisted, RIG now sends out a `rig.session_killed` event before closing the socket. For WebSocket connections, the closing frame contains "Session killed." as its payload.
14
-
- New API for querying and updating the session blacklist: `/v2/session-blacklist`, which introduces the following breaking changes:
31
+
- New API for querying and updating the session blacklist: `/v2/session-blacklist`, which introduces the following breaking changes (`/v1/session-blacklist` is unaffected):
15
32
- When a session has been added to the session blacklist successfully, the endpoint now uses the correct HTTP status code "201 Created" instead of "200 Ok".
16
33
- When using the API to blacklist a session, the `validityInSeconds` should now be passed as an integer value (using a string still works though).
17
34
18
-
<!-- ### Changed -->
19
-
20
35
### Fixed
21
36
22
-
- Fixed usage of external check for `SUBMISSION_CHECK` and `SUBSCRIPTION_CHECK`. [#241](https://github.com/Accenture/reactive-interaction-gateway/issues/241)
37
+
- Fixed usage of external check for `SUBMISSION_CHECK` and `SUBSCRIPTION_CHECK`.
- Fixed HTTP response for `DELETE 4010/v1/apis/api_id` and `DELETE 4010/v2/apis/api_id` to correctly return `204` and no content.
26
42
27
-
<!-- ### Deprecated -->
28
-
29
43
### Removed
30
44
31
45
- Removed the `JWT_BLACKLIST_DEFAULT_EXPIRY_HOURS` environment variable ([deprecated since 2.0.0-beta.2](https://github.com/Accenture/reactive-interaction-gateway/commit/f974533455aa3ebc550ee95bf291585925a406d5)).
- A connection is now associated to its session right after the connection is established, given the request carries a JWT in its authorization header. Previously, this was only done by the subscriptions endpoint, which could cause a connection to remain active even after blacklisting its authorization token.
0 commit comments