[ https://issues.apache.org/jira/browse/MEECROWAVE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592567#comment-16592567 ]
Romain Manni-Bucau edited comment on MEECROWAVE-137 at 8/25/18 12:19 PM: ------------------------------------------------------------------------- It is surely not well documented but you can already configure valves through properties: [https://github.com/apache/meecrowave/blob/trunk/meecrowave-core/src/test/java/org/apache/meecrowave/ValveTest.java#L43] was (Author: romain.manni-bucau): S is surely not well documented but you can already configure valves through properties: https://github.com/apache/meecrowave/blob/trunk/meecrowave-core/src/test/java/org/apache/meecrowave/ValveTest.java#L43 > default remote-ip-valve setup options > ------------------------------------- > > Key: MEECROWAVE-137 > URL: https://issues.apache.org/jira/browse/MEECROWAVE-137 > Project: Meecrowave > Issue Type: New Feature > Affects Versions: 1.2.3 > Reporter: Terefang Verigorn > Priority: Trivial > > one of the common use cases is to put tomcat behind a ssl-offloader. > to receive proper headers, attributes and redirection there is the > remoteipvalve. > spring boot already has this feature covered as documented here: > [https://docs.spring.io/spring-boot/docs/current-SNAPSHOT/reference/htmlsingle/#howto-use-tomcat-behind-a-proxy-server] > i propose that, if any of the following options are present, to trigger the > auto-setup of a remoteipvalve within meecrowave: > tomcat.remote-ip-header=x-your-remote-ip-header > tomcat.protocol-header=x-your-protocol-header > tomcat.internal-proxies=192\\.168\\.\\d\{1,3}\\.\\d\{1,3} > tomcat.use-forward-headers=true > -- This message was sent by Atlassian JIRA (v7.6.3#76005)