-
Updated
Aug 31, 2020 - Go
reverse-proxy
Here are 720 public repositories matching this topic...
-
Updated
Sep 2, 2020 - Go
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://
-
Updated
Aug 30, 2020 - Go
-
Updated
Aug 24, 2020 - Go
-
Updated
May 30, 2020 - Java
Active health check
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
-
Updated
Aug 30, 2020 - Shell
comments: apache/apisix#2121 (comment)
t/plugin/limit-req.t ..................... ok
# Failed test 'TEST 1: log rotate - response_body_like - response is expected (2020-08-31_10-25-32__access.log 2020-08-31_10-25-31__access.log 2020-08-31_10-25-33__access.log . 2020-08-31_10-25-32__error.log error.log 2020-08-31_10-25-33__error.log access.log 202
-
Updated
Jun 28, 2020 - Go
-
Updated
Jul 14, 2020 - Go
-
Updated
Sep 1, 2020 - C
-
Updated
Sep 2, 2020 - Go
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.
-
Updated
Sep 2, 2020 - C
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
-
Updated
Aug 31, 2020 - Go
-
Updated
Sep 2, 2020 - JavaScript
-
Updated
Jul 29, 2020 - C#
-
Updated
May 10, 2020 - Java
-
Updated
Aug 4, 2020 - Go
-
Updated
Dec 24, 2019 - JavaScript
-
Updated
Aug 22, 2018 - PHP
-
Updated
Dec 30, 2019
-
Updated
Aug 30, 2020 - Go
It would be nice to have a validation every time ergo runs in order to avoid badly formatted files and undefined errors.
-
Updated
Apr 5, 2020 - Go
Improve this page
Add a description, image, and links to the reverse-proxy topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the reverse-proxy topic, visit your repo's landing page and select "manage topics."
I would like to be able to prevent certain headers (Authorization: X-Auth-Token:, etc ) from being included in the caddy logs.
I found caddyserver/caddy#3562, which is asking to be able to set an allowlist of headers, which makes sense for their use case.
In my case, a blocklist, makes more sense, as I only want to prevent a single header from being included in the