v5.2.0-rc9

Update goreleaser.yml

v5.2.0-rc8

Update goreleaser.yml

v5.2.0-rc7

Update goreleaser.yml

v5.2.0-rc10

Update goreleaser.yml

Tyk Gateway v5.2.0 and Tyk Dashboard v5.2.0

Tyk Gateway 5.2.0

Tyk Dashboard 5.2.0

Tyk Gateway v5.0.6 and Tyk Dashboard v5.0.6

Tyk Gateway v5.0.6

Fixed

• Fixed a memory leak that occurred when setting the strict routes option to change the routing to avoid nearest-neighbour requests on overlapping routes (TYK_GW_HTTPSERVEROPTIONS_ENABLESTRICTROUTES)
• Improve the messages quality by remove useless msgs
• Fixed a bug where allowed/blocked IP validation error in API definition suppressed all other API definition validation errors
• Fixed a bug where the Gateway did not correctly close idle upstream connections (sockets) when configured to generate a new connection after a configurable period of time (using the max_conn_time configuration option). This could lead to the Gateway eventually running out of sockets under heavy load, impacting performance.
• Fixed a bug during Gateway reload where the Gateway would continue to load new API definitions even if policies failed to load; this would leave the customer at risk of an APIs being invoked without the correct policies having been loaded. Now Tyk will make a configurable number of attempts to load resources (APIs and policies) before continuing. If a resource fails to load, an error will be reported in the log and the Gateway will cancel the reload reverting to its previously working resource configuration.
  We have introduced two new variables to configure this behaviour:
  resource_sync.retry_attempts defines the number of retries that the Gateway should perform during a resource sync (APIs or policies), defaults to zero which means no retries are attempted
  resource_sync.interval configures the fixed interval between each retry attempt (in seconds)
• Remove the extra chunked transfer encoding that was added to rawResponse analytics
• Fixed a potential performance issue related to high rates of Gateway reloads (when the Gateway is updated due to a change in APIs and/or policies). The gateway uses a timer that ensures there at least one second between reloads, however in some scenarios this could lead to poor performance (for example overloading Redis). We have introduced a new configuration option reload_interval that can be used to adjust the duration between reloads and hence optimise the performance of your Tyk deployment.

Tyk Dashboard v5.0.6

Fixed

• Fixed the Tyk Dashboard API so that Tyk Sync can fully support Tyk OAS APIs; this will be enabled from Tyk Sync version 1.4.1.
• Emit a signal of API change when the OAS migration script is executed, to notify data planes about the change in API structure in database
• Fixed a bug where a negative value could be provided in the Enforced Timeout configuration
• Fix Log Browser performance issue with MongoDB. It should display logs for selected time period only.
• Fixed a bug where the Dashboard would not allow you to modify a key that provides access rights to an inactive API
• Fixed a bug in the Gateway usage chart in Dashboard analytics when selecting the "show analytics for " dropdown option
• Fix: User should use URL-encoded values in username and password of a MongoDB connection string if it contains following characters - "?", "@". The same connection string should always be accepted by both mgo and mongo-go drivers.

Tyk Gateway 4.3.8

Tyk Gateway 4.3.8

Fixed

• Fixed a bug where gateway does not load api's and policies on cold start when MDCB is down
• Fixed a bug where gateway didn't properly closed idle connections
• Fixed a bug where enable_stric_routes option caused memory leak on reload action

Changed

• Default RPC poll size is 5

v4.3.8-alpha8

Implement strict routes config option as a middleware rather than a custom handler

v4.3.8-alpha7

Remove muxer from explicitRouteHandler struct

v4.3.8-alpha3

Assign this ThisHandler on the chainObj