You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Venkatesh Sellappa (JIRA)" <ji...@apache.org> on 2015/10/16 21:25:05 UTC
[jira] [Comment Edited] (NIFI-747) ListenHTTP should expose
property for the URL path to accept data on
[ https://issues.apache.org/jira/browse/NIFI-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961235#comment-14961235 ]
Venkatesh Sellappa edited comment on NIFI-747 at 10/16/15 7:24 PM:
-------------------------------------------------------------------
I have done some work on this and tested it. The fix is quite straightforward using jax-ws paths.
The code is here https://github.com/vs186031/nifi/tree/nifi-747 and submitted a pull request to the main tree.
was (Author: vs186031):
I have done some work on this and tested it. The fix is quite straightforward using relative paths.
The code is here https://github.com/vs186031/nifi/tree/nifi-747 and submitted a pull request to the main tree.
> ListenHTTP should expose property for the URL path to accept data on
> --------------------------------------------------------------------
>
> Key: NIFI-747
> URL: https://issues.apache.org/jira/browse/NIFI-747
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Labels: beginner, newbie
> Fix For: 0.4.0
>
>
> When using ListenHTTP, you have to post to http(s)://<hostname>:<port>/contentListener
> The /contentListener part is often problematic, as it's often mistyped and really serves no purpose, since the processor starts an embedded web server with only a single servlet.
> We cannot remove the "/contentListener" path because we need to maintain backward compatibility. However, we can provide a new property to configure it, setting the default to "/contentListener". This way, when a user adds a ListenHTTP Processor, he/she can change the path to "/"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)