You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2014/11/05 11:28:33 UTC

[jira] [Resolved] (FLUME-678) Enable configuration to control the jetty server.

     [ https://issues.apache.org/jira/browse/FLUME-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashish Paliwal resolved FLUME-678.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s: v0.9.5

Won't fix. 0.X branch not maintained anymore

> Enable configuration to control the jetty server.
> -------------------------------------------------
>
>                 Key: FLUME-678
>                 URL: https://issues.apache.org/jira/browse/FLUME-678
>             Project: Flume
>          Issue Type: New Feature
>    Affects Versions: v0.9.4
>            Reporter: Jonathan Hsieh
>             Fix For: v0.9.5
>
>
> If agents are on externally facing machines, exposing a port with internals information is a potential security issue.  Currently there is command line mechanism that prevents the webserver from starting, but ideally this would be a static xml file configuration setting.  Moreover, it would be nice if users could control which applets are contained by the internal jetty server if it is on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)