api-gateway

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

Expected Behavior / New Feature

Support sticky sessions for ServiceDiscoveryProviders

Actual Behavior / Motivation for New Feature

When using websockets with ocelot in a distributed system, problem can arise since ocelot, as far as i know, doesn't support sticky sessions when working with service discovery providers.

The functionality could be great if it could work with both consul

Improved or typo fixed.

it shows we only support eureka.

Solution

we have supported:

Task

Currently, We use the AES algorithm to encrypt the password and provide the password back to the front end. I think It's not safe.

I suggest the following optimization:

1. The API does not return the password field. See `org.apache.shenyu.admin.controller.DashboardUse

Is your feature request related to a problem? Please describe.
The Datadog agent is deployed as a Daemonset. It expects the app/Envoy to push traces to the k8s node where the app runs.
Today, we cannot dynamically configure the Envoy configmap to target the host IP.

Describe the solution you'd like
In our Envoy wrapper dockerfile: https://github.com/solo-io/solo-projects/blob/18a7aa

Issue Summary

The stack generated has issues with the name of the regeneration queue when setting a domain name as name for the bucket (it doesn't pass the name constraints).

Actual behavior

The stack can not be created

Expected behavior

Be able to create the stack :)

Steps to reproduce

1. Create an app with some page that needs dynamic regeneration and try to put it o

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

sls invoke is useful for testing our API one request at a time.

It would be nice to spin up a local version of the API on localhost to enable us to develop our frontend apps against it, and to more easily run integration and E2E tests.