Re: Double-click action

[Lee Laim]

Swapping the vertex functions to a right-click menu would promote
drill-down consistency across components.

On Mon, Oct 24, 2016 at 12:26 PM, Andy LoPresto 
wrote:

> I’ll throw in that while I’ve never tried to double click anything other
> than a process group in the UI (so Lee’s information was welcome), Matt
> Burgess’ explanation of “drill down” is extremely intuitive to me and is
> exactly how my brain would reconcile the difference between double clicking
> a process group vs. a processor.
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Oct 24, 2016, at 11:18 AM, Russell Bateman  perfectsearchcorp.com> wrote:
>
> I'm sort of a new user, but I surely second Matt's expressed view. It's
> how I conceptualize it too.
>
> (My two cents.)
>
> Russ
>
> On 10/24/2016 09:03 AM, Rob Moran wrote:
>
> I think the logic Matt B described would make a lot of sense to experienced
> users, but it is changing behavior of the action and that *could* confuse
> new users.
>
> But as Lee brought up it is already being used differently, so it very well
> could be appreciated as learned behavior.
>
> It would be nice to expose common actions (like configure) on the faces of
> components so they are only a single click away. However, it would be tough
> to add more to them given current layouts.
>
> Rob
>
> On Mon, Oct 24, 2016 at 10:49 AM, Matt Gilman 
> wrote:
>
> Certainly not the first time this has been brought up... in fact, there's
> already a JIRA for it [1]. Use of double click on the connection is a great
> counter point for consistency between the components.
>
> [1] https://issues.apache.org/jira/browse/NIFI-1580
>
> On Mon, Oct 24, 2016 at 10:45 AM, Lee Laim  wrote:
>
> Don't forget about connection behavior.
>
> Double-click on a connection places a movable vertex on the connection.
> Double-click on a vertex deletes it.
>
> Very intuitive once you realize it's there.
>
> Lee
>
>
> On Oct 24, 2016, at 8:21 AM, McDermott, Chris Kevin (MSDU -
>
> STaTS/StorefrontRemote)  wrote:
>
> I like this, Matt.  It has often find myself double clicking to try to
>
> configure, or view configuration.  It just seems natural.
>
>
> Chris McDermott
>
> Remote Business Analytics
> STaTS/StoreFront Remote
> HPE Storage
> Hewlett Packard Enterprise
> Mobile: +1 978-697-5315
>
>
>
> On 10/24/16, 9:50 AM, "Matt Burgess"  wrote:
>
>+1 for avoiding confusion or changing existing behavior, but I
>
> think a
>
>good compromise is to leave the Configure option on both context
>
> menus
>
>(right-click, e.g.) and add the double-click behavior to the
>
> Processor
>
>to open the configuration dialog. In that case, the default
>(double-click) option for both Processors and Process Groups is no
>longer "nothing" and "Enter Group" respectively; rather it is
>conceptually something like "Drill-down". For PGs drill-down is
>
> Enter
>
>Group, for Processors you can't drill down any further than the
>
> config
>
>dialog, so that becomes the default action for double-click.
>
>Thoughts? Thanks,
>Matt
>
>On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
> wrote:
>
> Yep, that's a good point and I agree we should avoid confusion with
> different behaviors depending of the components.
>
> Thanks Matt!
>
> Pierre
>
> 2016-10-24 13:44 GMT+02:00 Matt Gilman :
>
> Pierre,
>
> Currently the double click action is used to enter a Process Group.
> There's been discussion in the past on this mailing about possibly
>
> using it
>
> to configure. My only hesitation there would be the inconsistency
>
> between
>
> action on the different components. Unless of course we also switch
>
> the
>
> action for entering a group. Then I start to worry about confusing
>
> the
>
> user
>
> with changing up the existing behavior too much.
>
> Matt
>
> Sent from my iPhone
>
> On Oct 24, 2016, at 7:39 AM, Pierre Villard <
>
> pierre.villard...@gmail.com>
>
> wrote:
>
> Hi,
>
> I was wondering if there is any reason why the double click action
>
> is
>
> not
>
> used in the UI? I think this could be a nice shortcut to access
> "Configure/View configuration" view from elements on the canvas.
>
> Thoughts?
>
> Pierre
>
>
>
>
>

Re: Nifi 1.0.0 - HTTPS

[skunky]

Sir,
It worked !
Thank you very much for help.




--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-1-0-0-HTTPS-tp13683p13708.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: Double-click action

[Andy LoPresto]

I’ll throw in that while I’ve never tried to double click anything other than a 
process group in the UI (so Lee’s information was welcome), Matt Burgess’ 
explanation of “drill down” is extremely intuitive to me and is exactly how my 
brain would reconcile the difference between double clicking a process group 
vs. a processor.

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Oct 24, 2016, at 11:18 AM, Russell Bateman 
>  wrote:
> 
> I'm sort of a new user, but I surely second Matt's expressed view. It's how I 
> conceptualize it too.
> 
> (My two cents.)
> 
> Russ
> 
> On 10/24/2016 09:03 AM, Rob Moran wrote:
>> I think the logic Matt B described would make a lot of sense to experienced
>> users, but it is changing behavior of the action and that *could* confuse
>> new users.
>> 
>> But as Lee brought up it is already being used differently, so it very well
>> could be appreciated as learned behavior.
>> 
>> It would be nice to expose common actions (like configure) on the faces of
>> components so they are only a single click away. However, it would be tough
>> to add more to them given current layouts.
>> 
>> Rob
>> 
>> On Mon, Oct 24, 2016 at 10:49 AM, Matt Gilman 
>> wrote:
>> 
>>> Certainly not the first time this has been brought up... in fact, there's
>>> already a JIRA for it [1]. Use of double click on the connection is a great
>>> counter point for consistency between the components.
>>> 
>>> [1] https://issues.apache.org/jira/browse/NIFI-1580
>>> 
>>> On Mon, Oct 24, 2016 at 10:45 AM, Lee Laim  wrote:
>>> 
 Don't forget about connection behavior.
 
 Double-click on a connection places a movable vertex on the connection.
 Double-click on a vertex deletes it.
 
 Very intuitive once you realize it's there.
 
 Lee
 
 
> On Oct 24, 2016, at 8:21 AM, McDermott, Chris Kevin (MSDU -
 STaTS/StorefrontRemote)  wrote:
> I like this, Matt.  It has often find myself double clicking to try to
 configure, or view configuration.  It just seems natural.
> 
> Chris McDermott
> 
> Remote Business Analytics
> STaTS/StoreFront Remote
> HPE Storage
> Hewlett Packard Enterprise
> Mobile: +1 978-697-5315
> 
> 
> 
> On 10/24/16, 9:50 AM, "Matt Burgess"  wrote:
> 
>+1 for avoiding confusion or changing existing behavior, but I
>>> think a
>good compromise is to leave the Configure option on both context
>>> menus
>(right-click, e.g.) and add the double-click behavior to the
>>> Processor
>to open the configuration dialog. In that case, the default
>(double-click) option for both Processors and Process Groups is no
>longer "nothing" and "Enter Group" respectively; rather it is
>conceptually something like "Drill-down". For PGs drill-down is
>>> Enter
>Group, for Processors you can't drill down any further than the
>>> config
>dialog, so that becomes the default action for double-click.
> 
>Thoughts? Thanks,
>Matt
> 
>On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
> wrote:
>> Yep, that's a good point and I agree we should avoid confusion with
>> different behaviors depending of the components.
>> 
>> Thanks Matt!
>> 
>> Pierre
>> 
>> 2016-10-24 13:44 GMT+02:00 Matt Gilman :
>> 
>>> Pierre,
>>> 
>>> Currently the double click action is used to enter a Process Group.
>>> There's been discussion in the past on this mailing about possibly
 using it
>>> to configure. My only hesitation there would be the inconsistency
 between
>>> action on the different components. Unless of course we also switch
>>> the
>>> action for entering a group. Then I start to worry about confusing
>>> the
 user
>>> with changing up the existing behavior too much.
>>> 
>>> Matt
>>> 
>>> Sent from my iPhone
>>> 
 On Oct 24, 2016, at 7:39 AM, Pierre Villard <
 pierre.villard...@gmail.com>
>>> wrote:
 Hi,
 
 I was wondering if there is any reason why the double click action
>>> is
 not
 used in the UI? I think this could be a nice shortcut to access
 "Configure/View configuration" view from elements on the canvas.
>>> Thoughts?
 Pierre
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Double-click action

[Russell Bateman]

I'm sort of a new user, but I surely second Matt's expressed view. It's 
how I conceptualize it too.


(My two cents.)

Russ

On 10/24/2016 09:03 AM, Rob Moran wrote:

I think the logic Matt B described would make a lot of sense to experienced
users, but it is changing behavior of the action and that *could* confuse
new users.

But as Lee brought up it is already being used differently, so it very well
could be appreciated as learned behavior.

It would be nice to expose common actions (like configure) on the faces of
components so they are only a single click away. However, it would be tough
to add more to them given current layouts.

Rob

On Mon, Oct 24, 2016 at 10:49 AM, Matt Gilman 
wrote:


Certainly not the first time this has been brought up... in fact, there's
already a JIRA for it [1]. Use of double click on the connection is a great
counter point for consistency between the components.

[1] https://issues.apache.org/jira/browse/NIFI-1580

On Mon, Oct 24, 2016 at 10:45 AM, Lee Laim  wrote:


Don't forget about connection behavior.

Double-click on a connection places a movable vertex on the connection.
Double-click on a vertex deletes it.

Very intuitive once you realize it's there.

Lee



On Oct 24, 2016, at 8:21 AM, McDermott, Chris Kevin (MSDU -

STaTS/StorefrontRemote)  wrote:

I like this, Matt.  It has often find myself double clicking to try to

configure, or view configuration.  It just seems natural.


Chris McDermott

Remote Business Analytics
STaTS/StoreFront Remote
HPE Storage
Hewlett Packard Enterprise
Mobile: +1 978-697-5315



On 10/24/16, 9:50 AM, "Matt Burgess"  wrote:

+1 for avoiding confusion or changing existing behavior, but I

think a

good compromise is to leave the Configure option on both context

menus

(right-click, e.g.) and add the double-click behavior to the

Processor

to open the configuration dialog. In that case, the default
(double-click) option for both Processors and Process Groups is no
longer "nothing" and "Enter Group" respectively; rather it is
conceptually something like "Drill-down". For PGs drill-down is

Enter

Group, for Processors you can't drill down any further than the

config

dialog, so that becomes the default action for double-click.

Thoughts? Thanks,
Matt

On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
 wrote:

Yep, that's a good point and I agree we should avoid confusion with
different behaviors depending of the components.

Thanks Matt!

Pierre

2016-10-24 13:44 GMT+02:00 Matt Gilman :


Pierre,

Currently the double click action is used to enter a Process Group.
There's been discussion in the past on this mailing about possibly

using it

to configure. My only hesitation there would be the inconsistency

between

action on the different components. Unless of course we also switch

the

action for entering a group. Then I start to worry about confusing

the

user

with changing up the existing behavior too much.

Matt

Sent from my iPhone


On Oct 24, 2016, at 7:39 AM, Pierre Villard <

pierre.villard...@gmail.com>

wrote:

Hi,

I was wondering if there is any reason why the double click action

is

not

used in the UI? I think this could be a nice shortcut to access
"Configure/View configuration" view from elements on the canvas.

Thoughts?

Pierre

Re: Double-click action

[Rob Moran]

I think the logic Matt B described would make a lot of sense to experienced
users, but it is changing behavior of the action and that *could* confuse
new users.

But as Lee brought up it is already being used differently, so it very well
could be appreciated as learned behavior.

It would be nice to expose common actions (like configure) on the faces of
components so they are only a single click away. However, it would be tough
to add more to them given current layouts.

Rob

On Mon, Oct 24, 2016 at 10:49 AM, Matt Gilman 
wrote:

> Certainly not the first time this has been brought up... in fact, there's
> already a JIRA for it [1]. Use of double click on the connection is a great
> counter point for consistency between the components.
>
> [1] https://issues.apache.org/jira/browse/NIFI-1580
>
> On Mon, Oct 24, 2016 at 10:45 AM, Lee Laim  wrote:
>
> > Don't forget about connection behavior.
> >
> > Double-click on a connection places a movable vertex on the connection.
> > Double-click on a vertex deletes it.
> >
> > Very intuitive once you realize it's there.
> >
> > Lee
> >
> >
> > > On Oct 24, 2016, at 8:21 AM, McDermott, Chris Kevin (MSDU -
> > STaTS/StorefrontRemote)  wrote:
> > >
> > > I like this, Matt.  It has often find myself double clicking to try to
> > configure, or view configuration.  It just seems natural.
> > >
> > >
> > > Chris McDermott
> > >
> > > Remote Business Analytics
> > > STaTS/StoreFront Remote
> > > HPE Storage
> > > Hewlett Packard Enterprise
> > > Mobile: +1 978-697-5315
> > >
> > >
> > >
> > > On 10/24/16, 9:50 AM, "Matt Burgess"  wrote:
> > >
> > >+1 for avoiding confusion or changing existing behavior, but I
> think a
> > >good compromise is to leave the Configure option on both context
> menus
> > >(right-click, e.g.) and add the double-click behavior to the
> Processor
> > >to open the configuration dialog. In that case, the default
> > >(double-click) option for both Processors and Process Groups is no
> > >longer "nothing" and "Enter Group" respectively; rather it is
> > >conceptually something like "Drill-down". For PGs drill-down is
> Enter
> > >Group, for Processors you can't drill down any further than the
> config
> > >dialog, so that becomes the default action for double-click.
> > >
> > >Thoughts? Thanks,
> > >Matt
> > >
> > >On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
> > > wrote:
> > >> Yep, that's a good point and I agree we should avoid confusion with
> > >> different behaviors depending of the components.
> > >>
> > >> Thanks Matt!
> > >>
> > >> Pierre
> > >>
> > >> 2016-10-24 13:44 GMT+02:00 Matt Gilman :
> > >>
> > >>> Pierre,
> > >>>
> > >>> Currently the double click action is used to enter a Process Group.
> > >>> There's been discussion in the past on this mailing about possibly
> > using it
> > >>> to configure. My only hesitation there would be the inconsistency
> > between
> > >>> action on the different components. Unless of course we also switch
> the
> > >>> action for entering a group. Then I start to worry about confusing
> the
> > user
> > >>> with changing up the existing behavior too much.
> > >>>
> > >>> Matt
> > >>>
> > >>> Sent from my iPhone
> > >>>
> >  On Oct 24, 2016, at 7:39 AM, Pierre Villard <
> > pierre.villard...@gmail.com>
> > >>> wrote:
> > 
> >  Hi,
> > 
> >  I was wondering if there is any reason why the double click action
> is
> > not
> >  used in the UI? I think this could be a nice shortcut to access
> >  "Configure/View configuration" view from elements on the canvas.
> > >>> Thoughts?
> > 
> >  Pierre
> > >>>
> > >
> > >
> >
>

Re: Double-click action

[Matt Gilman]

Certainly not the first time this has been brought up... in fact, there's
already a JIRA for it [1]. Use of double click on the connection is a great
counter point for consistency between the components.

[1] https://issues.apache.org/jira/browse/NIFI-1580

On Mon, Oct 24, 2016 at 10:45 AM, Lee Laim  wrote:

> Don't forget about connection behavior.
>
> Double-click on a connection places a movable vertex on the connection.
> Double-click on a vertex deletes it.
>
> Very intuitive once you realize it's there.
>
> Lee
>
>
> > On Oct 24, 2016, at 8:21 AM, McDermott, Chris Kevin (MSDU -
> STaTS/StorefrontRemote)  wrote:
> >
> > I like this, Matt.  It has often find myself double clicking to try to
> configure, or view configuration.  It just seems natural.
> >
> >
> > Chris McDermott
> >
> > Remote Business Analytics
> > STaTS/StoreFront Remote
> > HPE Storage
> > Hewlett Packard Enterprise
> > Mobile: +1 978-697-5315
> >
> >
> >
> > On 10/24/16, 9:50 AM, "Matt Burgess"  wrote:
> >
> >+1 for avoiding confusion or changing existing behavior, but I think a
> >good compromise is to leave the Configure option on both context menus
> >(right-click, e.g.) and add the double-click behavior to the Processor
> >to open the configuration dialog. In that case, the default
> >(double-click) option for both Processors and Process Groups is no
> >longer "nothing" and "Enter Group" respectively; rather it is
> >conceptually something like "Drill-down". For PGs drill-down is Enter
> >Group, for Processors you can't drill down any further than the config
> >dialog, so that becomes the default action for double-click.
> >
> >Thoughts? Thanks,
> >Matt
> >
> >On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
> > wrote:
> >> Yep, that's a good point and I agree we should avoid confusion with
> >> different behaviors depending of the components.
> >>
> >> Thanks Matt!
> >>
> >> Pierre
> >>
> >> 2016-10-24 13:44 GMT+02:00 Matt Gilman :
> >>
> >>> Pierre,
> >>>
> >>> Currently the double click action is used to enter a Process Group.
> >>> There's been discussion in the past on this mailing about possibly
> using it
> >>> to configure. My only hesitation there would be the inconsistency
> between
> >>> action on the different components. Unless of course we also switch the
> >>> action for entering a group. Then I start to worry about confusing the
> user
> >>> with changing up the existing behavior too much.
> >>>
> >>> Matt
> >>>
> >>> Sent from my iPhone
> >>>
>  On Oct 24, 2016, at 7:39 AM, Pierre Villard <
> pierre.villard...@gmail.com>
> >>> wrote:
> 
>  Hi,
> 
>  I was wondering if there is any reason why the double click action is
> not
>  used in the UI? I think this could be a nice shortcut to access
>  "Configure/View configuration" view from elements on the canvas.
> >>> Thoughts?
> 
>  Pierre
> >>>
> >
> >
>

Re: Double-click action

[McDermott, Chris Kevin (MSDU - STaTS/StorefrontRemote)]

I like this, Matt.  It has often find myself double clicking to try to 
configure, or view configuration.  It just seems natural.


Chris McDermott
 
Remote Business Analytics
STaTS/StoreFront Remote
HPE Storage
Hewlett Packard Enterprise
Mobile: +1 978-697-5315
 


On 10/24/16, 9:50 AM, "Matt Burgess"  wrote:

+1 for avoiding confusion or changing existing behavior, but I think a
good compromise is to leave the Configure option on both context menus
(right-click, e.g.) and add the double-click behavior to the Processor
to open the configuration dialog. In that case, the default
(double-click) option for both Processors and Process Groups is no
longer "nothing" and "Enter Group" respectively; rather it is
conceptually something like "Drill-down". For PGs drill-down is Enter
Group, for Processors you can't drill down any further than the config
dialog, so that becomes the default action for double-click.

Thoughts? Thanks,
Matt

On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
 wrote:
> Yep, that's a good point and I agree we should avoid confusion with
> different behaviors depending of the components.
>
> Thanks Matt!
>
> Pierre
>
> 2016-10-24 13:44 GMT+02:00 Matt Gilman :
>
>> Pierre,
>>
>> Currently the double click action is used to enter a Process Group.
>> There's been discussion in the past on this mailing about possibly using 
it
>> to configure. My only hesitation there would be the inconsistency between
>> action on the different components. Unless of course we also switch the
>> action for entering a group. Then I start to worry about confusing the 
user
>> with changing up the existing behavior too much.
>>
>> Matt
>>
>> Sent from my iPhone
>>
>> > On Oct 24, 2016, at 7:39 AM, Pierre Villard 

>> wrote:
>> >
>> > Hi,
>> >
>> > I was wondering if there is any reason why the double click action is 
not
>> > used in the UI? I think this could be a nice shortcut to access
>> > "Configure/View configuration" view from elements on the canvas.
>> Thoughts?
>> >
>> > Pierre
>>

Re: Double-click action

[Matt Burgess]

+1 for avoiding confusion or changing existing behavior, but I think a
good compromise is to leave the Configure option on both context menus
(right-click, e.g.) and add the double-click behavior to the Processor
to open the configuration dialog. In that case, the default
(double-click) option for both Processors and Process Groups is no
longer "nothing" and "Enter Group" respectively; rather it is
conceptually something like "Drill-down". For PGs drill-down is Enter
Group, for Processors you can't drill down any further than the config
dialog, so that becomes the default action for double-click.

Thoughts? Thanks,
Matt

On Mon, Oct 24, 2016 at 7:49 AM, Pierre Villard
 wrote:
> Yep, that's a good point and I agree we should avoid confusion with
> different behaviors depending of the components.
>
> Thanks Matt!
>
> Pierre
>
> 2016-10-24 13:44 GMT+02:00 Matt Gilman :
>
>> Pierre,
>>
>> Currently the double click action is used to enter a Process Group.
>> There's been discussion in the past on this mailing about possibly using it
>> to configure. My only hesitation there would be the inconsistency between
>> action on the different components. Unless of course we also switch the
>> action for entering a group. Then I start to worry about confusing the user
>> with changing up the existing behavior too much.
>>
>> Matt
>>
>> Sent from my iPhone
>>
>> > On Oct 24, 2016, at 7:39 AM, Pierre Villard 
>> wrote:
>> >
>> > Hi,
>> >
>> > I was wondering if there is any reason why the double click action is not
>> > used in the UI? I think this could be a nice shortcut to access
>> > "Configure/View configuration" view from elements on the canvas.
>> Thoughts?
>> >
>> > Pierre
>>

Re: Double-click action

[Pierre Villard]

Yep, that's a good point and I agree we should avoid confusion with
different behaviors depending of the components.

Thanks Matt!

Pierre

2016-10-24 13:44 GMT+02:00 Matt Gilman :

> Pierre,
>
> Currently the double click action is used to enter a Process Group.
> There's been discussion in the past on this mailing about possibly using it
> to configure. My only hesitation there would be the inconsistency between
> action on the different components. Unless of course we also switch the
> action for entering a group. Then I start to worry about confusing the user
> with changing up the existing behavior too much.
>
> Matt
>
> Sent from my iPhone
>
> > On Oct 24, 2016, at 7:39 AM, Pierre Villard 
> wrote:
> >
> > Hi,
> >
> > I was wondering if there is any reason why the double click action is not
> > used in the UI? I think this could be a nice shortcut to access
> > "Configure/View configuration" view from elements on the canvas.
> Thoughts?
> >
> > Pierre
>

Re: Double-click action

[Matt Gilman]

Pierre,

Currently the double click action is used to enter a Process Group. There's 
been discussion in the past on this mailing about possibly using it to 
configure. My only hesitation there would be the inconsistency between action 
on the different components. Unless of course we also switch the action for 
entering a group. Then I start to worry about confusing the user with changing 
up the existing behavior too much.

Matt

Sent from my iPhone

> On Oct 24, 2016, at 7:39 AM, Pierre Villard  
> wrote:
> 
> Hi,
> 
> I was wondering if there is any reason why the double click action is not
> used in the UI? I think this could be a nice shortcut to access
> "Configure/View configuration" view from elements on the canvas. Thoughts?
> 
> Pierre

Double-click action

[Pierre Villard]

Hi,

I was wondering if there is any reason why the double click action is not
used in the UI? I think this could be a nice shortcut to access
"Configure/View configuration" view from elements on the canvas. Thoughts?

Pierre

Re: Posting file and form params as multipart/form-data

[Pierre Villard]

Hi Rupert,

Could you give more details about how you have used InvokeHTTP processor?

The content of the incoming flow file will be used as content of the
request sent by InvokeHTTP processor and you can define all the parameters
in the processor.  What I am not sure to understand is "the other params
are not sent", what do you mean?

Thanks,
Pierre

2016-10-22 7:23 GMT+02:00 rupert :

> Hi,
>
> I've tried to figure out how to post a file that I picked up with the
> GetFile processor as well as some additional params with a
> multipart/form-data Content-Type.
> I tried to use the InvokeHTTP and the PostHTTP method put if I send the
> content of the file as message body the other params are not sent.
>
> In CURL it works fine with this command:
> curl -v -X POST -F "project-file=@/home/schiessl/demos/test_file.xlsx" -F
> "format=binary/text/xml/xls/xlsx" http://requestb.in/1kurdbb1
>
> Any ideas on that?
>
> Rupert
>
>
>
>
> --
> View this message in context: http://apache-nifi-developer-
> list.39713.n7.nabble.com/Posting-file-and-form-params-
> as-multipart-form-data-tp13695.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>