reverse-proxy

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Current State

We currently hardcore the APISIX version in the blog or doc, which has misled some newcomers when they read an old blog version. This also makes updating the latest APISIX version in the doc harder, because we need to change several places.

Desired State

Let's add a static file containing the version numbers, and provide a simple one-liner command to get the version numbe

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

Description

• If the backend response is missing "Content-Type" header , try to perform MIME sniffing and fix the response header.

Reference

• http://mimesniff.spec.whatwg.org/
• https://github.com/bfenetworks/bfe/blob/develop/bfe_http/sniff.go

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

This is the logic currently implemented in the main branch:

If headers criteria are configured, a request is filtered in if it matches both headers and urls. If headers criteria are NOT configured, the probability options are used.

Describe the solution you'd like

I want to take the URL check when no header is

Describe the bug
Installation is successful, but the purging (dpkg --purge cloudflared) does not clean the service

$ ls /etc/systemd/system/cloudflared*
cloudflared.service 
cloudflared-update.service  
cloudflared-update.timer

nor config files:

$ ls /etc/cloudflared/
config.yml

therefore purge shows following errors:

dpkg: error processing package clou

Your Feature Request

Some applications are not case-sensitive on the URL parameters, and may look for arguments presented under any fantasist format. One could argue that we could turn the complete string to lower case before performing the lookup, but that would also change the values, which is not desired. A better approach would be to improve url_param, urlp, and urlp_val() to take a

The upstream issues got closed. It is referenced in:

• pipeline/authn/authenticator_oauth2_introspection_test.go#L857

This issue was created by the [ORY Closed Reference Notifier](https://github.com/or

Under multiport mode, plugins may need to know on which port was the request received/accepted. This information is currently not surfaced to plugins. For background also see abhinavsingh/proxy.py#535 (comment) thread