[jira] [Commented] (JCLOUDS-819) Allow prepending a custom user agent
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763856#comment-15763856
]
ASF subversion and git services commented on JCLOUDS-819:
-
Commit 79ad45d6b97f2879db40cd720764af237934a309 in jclouds's branch
refs/heads/2.0.x from [~vpanghal]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=79ad45d ]
Make user agent header configurable
Jclouds sends default user agent string with each request to cloud
services. But some of the application would like to overide this and
send custom user agent instead.
This commit define a string property to overide this default user agent
string. This property will be applied to all outgoing http request to
cloud services
JCLOUDS-819
> Allow prepending a custom user agent
>
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Reporter: Everett Toews
>Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
>.credentials(username, apiKey)
>.userAgent("users-app/0.1.2")
>.buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCLOUDS-819) Allow prepending a custom user agent
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763840#comment-15763840
]
ASF subversion and git services commented on JCLOUDS-819:
-
Commit f3c3f3b30620ad62dc502cf79bf121ec1773396e in jclouds's branch
refs/heads/master from [~vpanghal]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=f3c3f3b ]
Make user agent header configurable
Jclouds sends default user agent string with each request to cloud
services. But some of the application would like to overide this and
send custom user agent instead.
This commit define a string property to overide this default user agent
string. This property will be applied to all outgoing http request to
cloud services
JCLOUDS-819
> Allow prepending a custom user agent
>
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Reporter: Everett Toews
>Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
>.credentials(username, apiKey)
>.userAgent("users-app/0.1.2")
>.buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCLOUDS-819) Allow prepending a custom user agent
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752236#comment-15752236
]
Vijay Panghal commented on JCLOUDS-819:
---
[~nacx] [~zack-s] I have created a pull request for this. Can you please take a
look at this and provide feedback on this?
https://github.com/jclouds/jclouds/pull/1043
> Allow prepending a custom user agent
>
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Reporter: Everett Toews
>Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
>.credentials(username, apiKey)
>.userAgent("users-app/0.1.2")
>.buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCLOUDS-819) Allow prepending a custom user agent
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317160#comment-14317160
]
Everett Toews commented on JCLOUDS-819:
---
Me too. As long as it gets well documented.
> Allow prepending a custom user agent
>
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Reporter: Everett Toews
>Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
>.credentials(username, apiKey)
>.userAgent("users-app/0.1.2")
>.buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCLOUDS-819) Allow prepending a custom user agent
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316652#comment-14316652
]
Zack Shoylev commented on JCLOUDS-819:
--
I'm ok with using a property.
> Allow prepending a custom user agent
>
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Reporter: Everett Toews
>Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
>.credentials(username, apiKey)
>.userAgent("users-app/0.1.2")
>.buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCLOUDS-819) Allow prepending a custom user agent
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316471#comment-14316471
]
Ignasi Barrera commented on JCLOUDS-819:
I don't know if it is good to expose transport specific features in the
ContextBuilder. It should be used to describe the api or view being loaded, but
I wouldn't expose such concrete things there.
I'd rather use a context property or other mechanism to allow users to override
(or bind to the injector) the user agent.
> Allow prepending a custom user agent
>
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Reporter: Everett Toews
>Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
>.credentials(username, apiKey)
>.userAgent("users-app/0.1.2")
>.buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCLOUDS-819) Allow prepending a custom user agent
[
https://issues.apache.org/jira/browse/JCLOUDS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315594#comment-14315594
]
Zack Shoylev commented on JCLOUDS-819:
--
I will try to have a look at this later this week.
> Allow prepending a custom user agent
>
>
> Key: JCLOUDS-819
> URL: https://issues.apache.org/jira/browse/JCLOUDS-819
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Reporter: Everett Toews
>Priority: Minor
>
> Give your users the ability to _prepend_ a custom user agent. So if the
> existing user agent is "jclouds/1.8.1 java/1.7.0_51"
> Provide a method for your users to easily prepend their own user agent so
> they can further customize it. e.g. "users-app/0.1.2 jclouds/1.8.1
> java/1.7.0_51"
> This will give cloud providers much better insight into how people are using
> jclouds. This should be well documented and part of examples that are written
> for jclouds.
> It could be set like,
> {code}
> ComputeServiceContext context = ContextBuilder.newBuilder(PROVIDER)
>.credentials(username, apiKey)
>.userAgent("users-app/0.1.2")
>.buildView(ComputeServiceContext.class);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
