Caddy version: v2.2.0 h1:sMUFqTbVIRlmA8NkFnNt9l7s0e+0gw+7GPIrhty905A=

I am trying to pass pem-encoded client certificate to proxied service via a X-SSL-Cert header, like so:

sub.example.com {
    reverse_proxy 127.0.0.1:8000 {
        header_up X-SSL-Cert {http.request.tls.client.certificate_pem}
    }

    tls {
        client_auth {
            mode require
        }
    }
}

This list already excludes the services which use HSTS preloading or are redirected by current rulesets.

Alexa top 1M

• rediff.com (545)
• rackspace.com (1735)
• one.com (2011)
• privateemail.com (2273)
• freenet.de (3403)
• zoho.eu (3504)
• bluewin.ch (9624)
• lilo.org (15533)
• lycos.com (21102)
• goneo.de (35151)
• excite.com (58522

如：xxx app + www.xxx.com

不要在此issue里面提各种问题，谢谢配合。

Name of Issue

GET request of schema inputs throw error.
Workaround is to use POST or write middleware (example below)

• ActionHero Version: 16.0.5
• Node.js Version: 7.4.0
• Operating System OSX

Steps to reproduce your error

• Make a new actionhero project with ./node_modules/.bin/actionhero generate

./node_modules/.bin/actionhero generate action --name="schemaTest" 

Hi,

I saw that there is a perfomance degratation due to a for loop used inside the static func harmlessFunction() declared in CustomSelfAwareHelper struct.

This loop is trying to verify the type with the as? operator (that have a complexity of O(n) ) and try to unwrapp the result in order to call the awake() function.

For a medium-larger project (with likely 20k+ classes) that covers old

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