You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-auto@ws.apache.org by "Bogdan Sumanariu (JIRA)" <xm...@ws.apache.org> on 2008/08/05 14:30:44 UTC

[jira] Commented: (XMLRPC-149) customizable user agent header for the client

    [ https://issues.apache.org/jira/browse/XMLRPC-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619867#action_12619867 ] 

Bogdan Sumanariu commented on XMLRPC-149:
-----------------------------------------

Hi, I'm interested in the same patch. We are using the 3.1 library to connect to a server that requires a special User Agent.
Unfortunately the snapshot build is not available at the specified link. Please, can you republish it?

Thanks!

> 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
>            Assignee: Jochen Wiedmann
>             Fix For: 3.1.1
>
>         Attachments: xmlrpc-ua2.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.