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 "Andrew Norman (JIRA)" <xm...@ws.apache.org> on 2007/01/26 22:58:49 UTC
[jira] Created: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
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
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.
[jira] Reopened: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Andrew Norman (JIRA)" <xm...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Norman reopened XMLRPC-132:
----------------------------------
> 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: 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.
[jira] Updated: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Andrew Norman (JIRA)" <xm...@ws.apache.org>.
[ 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.zip
this is the proposed enhancement java files, made against the 3.0 code release and synchornized against the latest code in subversion
> 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: 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.
[jira] Updated: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Jochen Wiedmann (JIRA)" <xm...@ws.apache.org>.
[ 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.
[jira] Commented: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Andrew Norman (JIRA)" <xm...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488240 ]
Andrew Norman commented on XMLRPC-132:
--------------------------------------
Jochen,
sorry for the delay, but I've tested your version of the patch an it works with flying colors! Lets get this committed!
thanks for your time on this
-Andrew
> 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.
[jira] Resolved: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Andrew Norman (JIRA)" <xm...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Norman resolved XMLRPC-132.
----------------------------------
Resolution: Fixed
see submitted code
> 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: 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.
[jira] Reopened: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Andrew Norman (JIRA)" <xm...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Norman reopened XMLRPC-132:
----------------------------------
this nweeds to be reviewed and commited
> 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: 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.
[jira] Resolved: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Andrew Norman (JIRA)" <xm...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Norman resolved XMLRPC-132.
----------------------------------
Resolution: Fixed
> 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: 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.
[jira] Updated: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Andrew Norman (JIRA)" <xm...@ws.apache.org>.
[ 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: 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: 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.
[jira] Resolved: (XMLRPC-132) Enabling the ability for the xml-rpc
client to redirect requests
Posted by "Jochen Wiedmann (JIRA)" <xm...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/XMLRPC-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Wiedmann resolved XMLRPC-132.
------------------------------------
Resolution: Fixed
It's already in the trunk.
> 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.