[jira] [Updated] (NIFI-1342) PostHTTP User Agent property should be pre-populated with client default

2016-10-07 Thread Michael Moser (JIRA)

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

Michael Moser updated NIFI-1342:

Fix Version/s: (was: 0.8.0)
   0.7.1

> PostHTTP User Agent property should be pre-populated with client default
> 
>
> Key: NIFI-1342
> URL: https://issues.apache.org/jira/browse/NIFI-1342
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.4.1
>Reporter: Aldrin Piri
>Assignee: Pierre Villard
>Priority: Trivial
> Fix For: 1.1.0, 0.7.1
>
>
> Currently, PostHTTP shows an empty string for the User Agent property which 
> is used in web requests, but this actually results in the default of the 
> client being used.  For clarity, and if the backing library supports it, 
> getting the User Agent string used by the library as the default processor 
> User Agent property would be a nice improvement.



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


[jira] [Updated] (NIFI-1342) PostHTTP User Agent property should be pre-populated with client default

2016-09-15 Thread Oleg Zhurakousky (JIRA)

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

Oleg Zhurakousky updated NIFI-1342:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> PostHTTP User Agent property should be pre-populated with client default
> 
>
> Key: NIFI-1342
> URL: https://issues.apache.org/jira/browse/NIFI-1342
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.4.1
>Reporter: Aldrin Piri
>Assignee: Pierre Villard
>Priority: Trivial
> Fix For: 1.1.0, 0.8.0
>
>
> Currently, PostHTTP shows an empty string for the User Agent property which 
> is used in web requests, but this actually results in the default of the 
> client being used.  For clarity, and if the backing library supports it, 
> getting the User Agent string used by the library as the default processor 
> User Agent property would be a nice improvement.



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


[jira] [Updated] (NIFI-1342) PostHTTP User Agent property should be pre-populated with client default

2016-09-15 Thread Oleg Zhurakousky (JIRA)

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

Oleg Zhurakousky updated NIFI-1342:
---
Fix Version/s: 0.8.0
   1.1.0

> PostHTTP User Agent property should be pre-populated with client default
> 
>
> Key: NIFI-1342
> URL: https://issues.apache.org/jira/browse/NIFI-1342
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.4.1
>Reporter: Aldrin Piri
>Assignee: Pierre Villard
>Priority: Trivial
> Fix For: 1.1.0, 0.8.0
>
>
> Currently, PostHTTP shows an empty string for the User Agent property which 
> is used in web requests, but this actually results in the default of the 
> client being used.  For clarity, and if the backing library supports it, 
> getting the User Agent string used by the library as the default processor 
> User Agent property would be a nice improvement.



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


[jira] [Updated] (NIFI-1342) PostHTTP User Agent property should be pre-populated with client default

2016-09-14 Thread Pierre Villard (JIRA)

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

Pierre Villard updated NIFI-1342:
-
Status: Patch Available  (was: Open)

> PostHTTP User Agent property should be pre-populated with client default
> 
>
> Key: NIFI-1342
> URL: https://issues.apache.org/jira/browse/NIFI-1342
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.4.1
>Reporter: Aldrin Piri
>Priority: Trivial
>
> Currently, PostHTTP shows an empty string for the User Agent property which 
> is used in web requests, but this actually results in the default of the 
> client being used.  For clarity, and if the backing library supports it, 
> getting the User Agent string used by the library as the default processor 
> User Agent property would be a nice improvement.



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