I have modified the default file_server browse template to integrate it with a website, by using httpInclude to load blocks of HTML containing the header, footer and theme. These files are hosted on the same Caddy instance, and it works well provided that compression is not enabled. When compression is enabled, the file_server browser becomes garbage: it appears that raw compressed data is inc

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

Issue description

Hi, when I try to install Apache APISIX 2.9 on Mac (M1) accoding to those links[1][2], it failed due to reasons below:

lualogging 1.5.2-1 depends on luasocket (3.0rc1-2 installed)
lualogging 1.5.2-1 is now installed in /Users/juzhiyuan/workspace/apisix-2.9/apache-apisix-2.9-src/deps (license: MIT/X11)

casbin 1.26.0-1 depends on lrexlib-pcre >= 2.9.1 (not instal

Discussed in bfenetworks/bfe#844

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

Currently we have a mix of:

• Out of memory error.
• Out of memory error
• out of memory error
• out of memory
• out of memory.
• out of memory [some context]

All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller 😄

We are running a tunnel which is being accessed by clients using WARP.

tunnel: TUNNEL_ID
credentials-file: /var/lib/cloudflared/TUNNEL_ID.json
warp-routing:
  enabled: true
grace-period: 120s

The grace period is configured to 120 seconds, however this appears to not be respected when sending SIGTERM to cloudflared. The tunnel is stopped after 30 seconds, even though a c