Do you want to request a feature or report a bug?

Documentation improvement

In digestAuth documentation, Kubernetes section does not contain any useful example explaining how to put credentials into a file. The given example is same as users(using base

(Feature request out of https://caddy.community/t/use-placeholders-in-templates/7697)

I would like to see the ability of using placeholders like {http.error.status_code} in templates. This would allow us, for example, to create a single custom error page in nginx style. For now we have to create a page for every status code we would like to support (maybe using respond with include and ar

Summary

Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.

Additional Details

There are many use-cases that come to mind:

• Using environment variables inside the d

你好,我按照Readme配置好了server端,也成功的启动了, 但是登陆成功之后,直接又闪退回登陆界面.想问下是怎么回事. 具体操作我录了一个gif图片 如下.
http://linuxsogood.org/wp-content/uploads/2017/09/proxy.gif

github试了好几次都传不上来图片,所以放我个人博客了.
下面是日志.

`2017-09-11 03:17:54,741 INFO [org.fengfei.lanproxy.server.config.web.routes.RouteConfig] - <handle request for api /login>
2017-09-11 03:27:05,003 INFO [org.fengfei.lanproxy.server.config.web.routes.RouteConfig]

Description
Forward logs to a syslog listener to aggregate logs to a centralized service

• The server SHOULD limit the maximum number of resources to push.
• The depth of the selector SHOULD also be limited by the server.

In varnishadm 6.1, documentation of timeout_idle says:

varnishadm param.show timeout_idle timeout_idle

    Value is: 10.000 [seconds]
    Default is: 5.000
    Minimum is: 0.000

    Idle timeout for client connections.

    A connection is considered idle until we have received the full

Would love to know the QoS/RPS of this gateway. If you guys need help, I can have my team write something in locus. But if anyone has some reports on hardware => performance, would love to hear about it before making a decision on joining this community :).

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

We would like to support Graphite as a time series database when being used to front a dashboard.

There is a missing config parameter here:

https://developers.cloudflare.com/argo-tunnel/reference/arguments/

The id parameter is very useful to identify tunnels origin server, and it is the only config not visible in the documentation. I had to view the code to find it out.

Thanks in advance, i just lost 1 day of work around this 👍
Example config.yml

id: server_name_1
hostname:

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