Resgate Versions Save

A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.

v1.7.5

2 years ago

Go Version

  • 1.17.0

RES Protocol Version

  • 1.2.2

Release info

This release enhances Resgate by letting it utilize the header support introduced in NATS server v2.2, allowing it to instantly respond to clients with system.notFound when no services are listening on a requested subject.

Improvements

  • #219 Unsubscribe on delete
  • #222 NATS no responders support

v1.7.4

2 years ago

Go Version

  • 1.17.0

RES Protocol Version

  • 1.2.2

Release info

This release addresses a bug where Resgate could silently drop incoming NATS messages during heavy load bursts. It provides a new "bufferSize" configuration property, and increases its default value from 256 to 8192.

Fixes

  • #220 Slow consumer error not handled

v1.7.3

2 years ago

Go Version

  • 1.17.0

RES Protocol Version

  • 1.2.2

Release info

This release fixes a bug where Resgate could freeze on a system reset event affecting resource access, while having the resetThrottle option value > 0.

Fixes

  • #217 Deadlock on throttled access requests to same resource
  • #215 Resource response with HTTP logs error

v1.7.2

2 years ago

Go Version

  • 1.17.0

RES Protocol Version

  • 1.2.2

Release info

This release fixes a bug where Resgate could crash on a system reset event while having the resetThrottle option value > 0. If using reset throttling, it is highly recommended to upgrade Resgate to this version.

Fixes

  • #214 Throttle: negative running counter

v1.7.1

2 years ago

Go Version

  • 1.17.0

RES Protocol Version

  • 1.2.2

Release info

This release adds the option to throttle how many requests are sent when recursively following resource references for a subscription, to prevent flooding slower services with requests.

Features & improvements

  • #209 Reference throttling
  • #211 Added missing command flags

v1.7.0

2 years ago

Go Version

  • 1.17.0

RES Protocol Version

  • 1.2.2

Release info

This release introduces the new system token reset event that makes it easy to update or clear a client's token at any time, without the need to track connections.

Other requested features included in the release is NATS TLS and Root CAs support, and the throttling of requests on system reset events, to prevent flooding slower services on restarts.

Features & improvements

  • #177 NATS TLS and Root CA support
  • #187 Throttling reset requests
  • #202 Token ID and system token reset event
  • #203 Updated to Go 1.17.0

Fixes

  • #194 Possible client resource inconsistency

v1.6.3

3 years ago

Go Version

  • 1.14.4

RES Protocol Version

  • 1.2.1

Release info

Fixes a vulnerability where a long resource ID or method name (for call or auth requests) requested by a client would cause the NATS subject to exceed the maximum control line size, which in turn would disconnect Resgate from NATS. It would also would cause Resgate to fail to shut down properly.

This issue also affected HTTP requests with long URLs.

Fixes

  • #185 - Maximum control line size validation

v1.6.2

3 years ago

Go Version

  • 1.14.4

RES Protocol Version

  • 1.2.1

Release info

Fixes an issue where Resgate using headerAuth configuration didn't send the Access-Control-Allow-Credentials header in the response to HTTP requests.

Fixes

  • #181 CORS - Sending Access-Control-Allow-Credentials header
  • #183 Improve invalid value error message

v1.6.1

3 years ago

Go Version

  • 1.14.4

RES Protocol Version

  • 1.2.1

Release info

Fixes an issue where Resgate didn't set the Access-Control-Allow-Headers header in response to CORS preflight requests.

Fixes

  • #171 CORS - allowing Content-Type on headers

v1.6.0

3 years ago

Go Version

  • 1.14.4

RES Protocol Version

  • 1.2.1

Release info

This release introduces two new value types which have been requested by the community.

The first value type, soft resource references, enables links to resources which Resgate will not automatically embed in the response. Instead, the client can choose when (or if) the referenced resource is to be fetched.

The second value type, data values, allows for complex data such as objects, arrays, or deeply nested structures, to be used as values in a model or collection.

Features & improvements

  • #157 Soft resource references
  • #161 Unsubscribe count field
  • #165 Data values
  • #168 Updated to Go 1.14.4

Fixes

  • #158 Incorrect pre-response detection