Anup,
Could you be more explicit in how and what is failing? Is it the
ReplaceText? Is it the receiving web endpoint to which the POST is being
made? Are there any logs/bulletins that provide additional context?
I have a similar set up and seem to be getting the results I would expect:
Regular Expression: (.*)
Replacement Value: filename=${path}${filename}&appName=${appName}
Character Set: UTF-8
Maximum Buffer Size: 1 MB
Evaluation Mode: Entire text
This ReplaceText is done after a GenerateFlowFile and UpdateAttribute which
specifies an appName.
Also, are the *'s around your Replacement Value something you have added or
is that some formatting from the email? In the case of the prior, they are
not needed.
On Thu, Apr 30, 2015 at 3:05 AM, anup s <[email protected]> wrote:
> I tried doing that with the below entries.. but its failing.
>
> Regular ExpressionInfo = (.*)
> Replacement ValueInfo = *appName=myApp&filename=${path}${filename}*
> Character SetInfo = UTF-8
> Maximum Buffer SizeInfo = 1 MB
> Evaluation ModeInfo = Entire text
>
> How would these be treated as form parameters?
>
>
>
> --
> View this message in context:
> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Invoke-HTTP-POST-tp1290p1293.html
> Sent from the Apache NiFi (incubating) Developer List mailing list archive
> at Nabble.com.
>
