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

Issue description

The default_conn_delay of the limit-conn plug-in is used to control the delay of forwarding to upstreams when the connection exceeds a certain threshold, but after actual testing, it is found that this delay time is not strictly in accordance with the configured delay time.

https://github.com/openresty/lua-resty-limit-traffic/blob/master/lib/resty/limit/conn.lua#L98-L101

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

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Install gloo 1.8.1 with:

license_secret_name: myname
create_license_secret: false

Expected behavior
Gloo uses the provided secret, and then all subchart are updated too
Currently gloo works, but gloo-fed pods are failing because of non existent license with the default name

**Addi

Describe the bug

The rewrites configuration also supports an object, but this does not currently work in the default Lambda. https://nextjs.org/docs/api-reference/next.config.js/rewrites

Rewrites are applied after checking the filesystem (pages and /public files) and before dynamic routes by default. This behavior can be changed by instead returning an object instead of an array from t

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.