[ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.
atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Norman updated XMLRPC-132:
---------------------------------
Attachment: XMLRPC-132-patch
an eclipse patch file of the proposed feature
> Enabling the ability for the xml-rpc client to redirect
requests
>
------------------------------------------------------------
----
>
> Key: XMLRPC-132
> URL: http
s://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: 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.
|