https://github.com/caddyserver/caddy/blob/3ee663dee195e5f8ead7879b31131f46cd0fba13/modules/caddyhttp/reverseproxy/reverseproxy.go#L644-L653

As discussed on Reddit, it seems that reverse proxying some applications (in this case Plex) can lead to some extensive error log spamming. Requ

Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

Background

• BFE can be configured with Passive Health Check (i.e. Outlier Detection) and use responses from real requests to determine whether an backend instance is healthy.

Description
Add Active Health Check support:

• Actively and periodically send health checking requests to backend.
• Use responses from health checking requests to determine whether an backend instance is he

remove https://github.com/apache/apisix/blob/master/bin/apisix#L36 and
https://github.com/apache/apisix/blob/master/Makefile#L84, both of them are useless now.

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 "option forwardfor" cant't be unset, so there is no way to enable it in the default section and disable it in a particular frontend

It would be nice to have a validation every time ergo runs in order to avoid badly formatted files and undefined errors.