Tyk Gateway v5.2.1

Fixed

• Fixed a memory leak issue in Gateway 5.2.0 if opentelemetry is enabled. It was caused by multiple otelhttp handler being created. We have updated to use single instance of otelhttp handler in 5.2.1 to improve performance under high traffic load.
• 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)
• Updated panic message from Spanish to English
• Fixed a bug where missing http.response.body.size and http.request.body.size attributes to both Tyk HTTP span and upstream HTTP span. It is to allow users to have visibility on request and response size from the traces.
• 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 where HTTP APIs, when Persist GraphQL middleware was configured in conjunction with Response body transform, the body transformation of the response was not applied.
• 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 bug where, if you created a Key which provided access to an inactive or draft API, you would be unable to subsequently modify that Key (via the Dashboard or directly via the Tyk Gateway API)
• 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.
• Fixed a bug where headers not being passed upstream for GQL/UDG subscriptions

Tyk Dashboard v5.2.1

Fixed

• Fixed a bug where "Add GraphQL Operation" tickbox could not be disabled in GQL data source configuration screen, even if no operation was added. Now it's possible to change its state depending on the presence of GQL operation and variables.
• Fixed a bug in the Dashboard UI where pagination was breaking for lists using GraphQL requests
• 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.

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 5.2.0

Tyk Dashboard 5.2.0

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

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

Remove muxer from explicitRouteHandler struct

Tyk Gateway 5.1.2

Fixed

• Fixed a bug where the Gateway could panic when using Tyk OAS APIs with MDCB 2.3.0.
• Fixed a bug in the Dashboard's 'Most popular endpoints' section when using SQL Aggregate analytics
• Fixed a bug where the URL Rewrite middleware did not correctly handle escaped characters in the URL. Note that Tyk does not support a deliberate mix of escaped and non-escaped characters in the URL.
• Fixed a bug where api_name and api_id were not populated when using the Gateway API to retrieve policies.
• Fixed a bug where Kafka data source has been modified to work with the new version of resolver.Context

Tyk Dashboard 5.1.2

Fixed

• Fixed a bug where locking a Dashboard account also locked any Developer Portal account with the same username despite them being separate accounts.
• Fixed a bug where the order of APIs in the Versions List could change on browser refresh
• Fixed a security issue with password reset that could expose the names of all Organisations on the Tyk deployment
• Fixed a bug where it was possible to reset the Dashboard API access key from the /users endpoint; now this can only be reset using the key reset action.
• Optimised the loading and re-loading of APIs and Policies for complex scenarios
• Fixed a bug in the Dashboard's 'Most popular endpoints' section when using SQL Aggregate analytics
• Fixed a bug where mTLS request with an expired certificate allowed the request to be proxied upstream in static mTLS and dynamic mTLS

Tyk Gateway 5.0.5

Fixed

• Fixed a bug where the Gateway could panic when using Tyk OAS APIs with MDCB 2.3.0.
• Fixed a bug in the Dashboard's 'Most popular endpoints' section when using SQL Aggregate analytics
• Fixed a bug where the URL Rewrite middleware did not correctly handle escaped characters in the URL. Note that Tyk does not support a deliberate mix of escaped and non-escaped characters in the URL.
• Fixed a bug where api_name and api_id were not populated when using the Gateway API to retrieve policies.

Tyk Dashboard 5.0.5

Fixed

• Fixed a bug where locking a Dashboard account also locked any Developer Portal account with the same username despite them being separate accounts.
• Fixed a bug where the order of APIs in the Versions List could change on browser refresh
• Fixed a security issue with password reset that could expose the names of all Organisations on the Tyk deployment
• Fixed a bug where it was possible to reset the Dashboard API access key from the /users endpoint; now this can only be reset using the key reset action.
• Optimised the loading and re-loading of APIs and Policies for complex scenarios
• Fixed a bug in the Dashboard's 'Most popular endpoints' section when using SQL Aggregate analytics

Tyk Gateway 4.3.7

Fixed

• Fixed a bug where "disable_strip_slash" didn't worked for upstream requests