ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent Lintner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (RIPPLE-27) Method Patch is Not Supported for REST calls
Date Tue, 25 Jun 2013 21:13:19 GMT

     [ https://issues.apache.org/jira/browse/RIPPLE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brent Lintner resolved RIPPLE-27.
---------------------------------

    Resolution: Fixed
      Assignee: Brent Lintner

Thanks for the report. I did not know about the PATCH method :-) I think this will fix it
(I need a chance to be sure, as I just threw this up): https://github.com/apache/incubator-ripple/pull/10

However, the http://rippleapi.herokuapp.com proxy is currently owned by BlackBerry, and I
understand it is to be deprecated in the near future, so I doubt a new release could get pushed
by them (?).

For what it is worth, if you really want the feature (in the meantime), you can install the
CLI (NPM) package of Ripple by cloning the source, *or*, you can also install https://npmjs.org/package/ripple-emulator
when a new tag (of master) is unofficially pushed by a committer).
                
> Method Patch is Not Supported for REST calls
> --------------------------------------------
>
>                 Key: RIPPLE-27
>                 URL: https://issues.apache.org/jira/browse/RIPPLE-27
>             Project: Apache Ripple
>          Issue Type: Bug
>         Environment: Win 7/Chrome using ripple extension
>            Reporter: Sam Bosell
>            Assignee: Brent Lintner
>
> When trying to make webservice calls to the azure mobile services(ZUMO), updates are
sent using the PATCH method.  This is the error returned:
> Failed to load resource: Method PATCH is not allowed by Access-Control-Allow-Methods.
https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=https%3A//pmgtest.azure-mobile.net/tables/purchaseorder/1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message