[
https://issues.apache.org/jira/browse/XMLRPC-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530751
]
Andreas Sahlbach commented on XMLRPC-149:
-----------------------------------------
Could you tell me why? No offence, I just want to understand.
The transport factories already had an argument (XmlRpcClient) and they are
instantiated by the user. Therefore I thought it's a good place to put it in.
> customizable user agent header for the client
> ---------------------------------------------
>
> Key: XMLRPC-149
> URL: https://issues.apache.org/jira/browse/XMLRPC-149
> Project: XML-RPC
> Issue Type: Improvement
> Affects Versions: 3.1
> Environment: Gentoo / jdk 1.6
> Reporter: Andreas Sahlbach
> Attachments: xmlrpc-ua.patch
>
>
> Our client sets the user agent to an application string + version
> information. The user agent field can be easily read out at the web server
> and is an important information for the support and for statistics (how many
> old clients are still out there? how many customer have upgraded? is it true
> that the customer is using the new client or is he really using an old
> client, lying somewhere hidden in the classpath? etc.)
> Now we want to upgrade the xmlrpc lib to 3.1 and noticed that the user agent
> field is set by the library. Unfortunately it's not possible to customize
> this setting to our needs. I've added a patch that is allowing us to set the
> user agent to a string we are choosing. The code should be 100% compatible
> and there should be no negative side effects. Please consider to put this
> into the upstream as soon as possible. Thanks a lot!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
