[
https://issues.apache.org/jira/browse/XMLRPC-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617599#action_12617599
]
kent.narling edited comment on XMLRPC-149 at 7/28/08 3:32 PM:
--------------------------------------------------------------
Can anyone assist me on where to get this or a latest snapshot?
As a pre-built I mean...
Actually, I tried building the latest build, but get errors when trying to
compile, probably beccause I only use the 1.5 SDK.... (and the build seems to
require 1.3??)
And as a polite query: Is there an official 3.1.1 release planned soon? there
doesn't seem to be much activity...
was (Author: kent.narling):
Can anyone assist me on where to get this or a latest snapshot?
And as a polite query: Is there an official 3.1.1 release planned soon? there
doesn't seem to be much activity...
> 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.
