I suddenly find that I need this functionality (i.e. redirection handling) - badly.
Am I correct in assuming that it does not exist in any released version of Apache XML-RPC? It appears destined for 3.1. When is this release planned? Since my need is much too urgent to wait for this release, whenever it may be coming, what would be the best way to incorporate this fix and nothing else into my existing copy of XML-RPC 3.0? -----Original Message----- From: Andrew Norman [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 9:00 PM To: xmlrpc-dev@ws.apache.org Subject: RE: [jira] Updated: (XMLRPC-132) Enabling the ability for the xml-rpc client to redirect requests Should be able to verify in the next day or so. Will let you know how it goes -----Original Message----- From: Jochen Wiedmann (JIRA) [mailto:[EMAIL PROTECTED] Sent: Sunday, February 11, 2007 12:49 PM To: [EMAIL PROTECTED] Subject: [jira] Updated: (XMLRPC-132) Enabling the ability for the xml-rpc client to redirect requests [ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.atlassian.jira .plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann updated XMLRPC-132: ----------------------------------- Attachment: redirects.patch Sorry for the delay, but I am really doing my best to manage my backlog. Please verify the attached patch, which is based on yours, but drastically minimizes the impact. > Enabling the ability for the xml-rpc client to redirect requests > ---------------------------------------------------------------- > > Key: XMLRPC-132 > URL: https://issues.apache.org/jira/browse/XMLRPC-132 > Project: XML-RPC > Issue Type: New Feature > Components: Source > Affects Versions: 3.0, 3.1 > Reporter: Andrew Norman > Fix For: 3.1 > > Attachments: redirects.patch, XMLRPC-132-patch, XMLRPC-132.zip > > > This modification to the XMLRPCStreamTransport adds a customization point to determine if the transport needs to redirect the request before attempting to parse the response from the server. This uses a similar redirect algorithm as used in the Apache Http client to processing redirects with a Max limit to prevent a recursive loop. > The redirect logic itself is implemented in two callback methods isRedirectRequired() and > resetClientForRedirect() > These callback methods are only implemented in the XmlRpcCommonsTransport which means that the other transport options won't support redirects (unless they are modified to do this by implementing these call back methods) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
