[
https://issues.apache.org/jira/browse/NIFI-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962678#comment-14962678
]
Tony Kurc commented on NIFI-747:
--------------------------------
Just to document some of [~joewitt]'s concerns:
what happened if you tryed to POST to contentlistener/ in 0.3
{noformat}
2015-10-18 19:15:31,667 ERROR [Timer-Driven Process Thread-3]
o.a.nifi.processors.standard.PostHTTP
PostHTTP[id=d2d87bed-0f10-4e14-b53a-a9edc98249c4] Failed to Post
StandardFlowFileRecord[uuid=b8e8342f-8ff7-41ad-8734-6e00d8fa6c56,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1445209357841-1, container=default,
section=1], offset=26, length=6],offset=0,name=x.txt,size=6] to
http://localhost:12345/contentListener/: response code was 405:HTTP method POST
is not supported by this URL
{noformat}
> 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
> Assignee: Tony Kurc
> 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)
