Feature #11469

JSONP support

Added by Markus M almost 7 years ago. Updated over 4 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:REST API
Target version:2.1.0
Resolution:Fixed

Description

Please enable JSONP

This is necessary when a JS-Client wants to call the Redmine API of another Subdomain, Server, Protocol, Port... (Same Orign Policy)

It's not that hard to accomplish. You just need to set a request filter that wrappes the response in a given JS function. See #10761 for an example of the expected output.

Related issues

Related to Redmine - Defect #10761: Rest API JSON response can not be parsed by jQuery Closed
Related to Redmine - Feature #13718: Accept dots in JSONP callback Closed
Related to Redmine - Feature #12992: Make JSONP support optional and disabled by default Closed

Associated revisions

Revision 10088
Added by Jean-Philippe Lang almost 7 years ago

Adds JSONP support to the API (#11469).

History

#1 Updated by Etienne Massip almost 7 years ago

  • Category set to REST API

#2 Updated by Jean-Philippe Lang almost 7 years ago

  • Assignee set to Jean-Philippe Lang
  • Target version set to 2.1.0

#3 Updated by Jean-Philippe Lang almost 7 years ago

  • Subject changed from Enable JSONP to JSONP support
  • Status changed from New to Closed
  • Resolution set to Fixed

Support for JSONP added in r10088. You can use the callback or jsonp parameter to specify the JSONP callback.

Exemple:

GET /issues.json?callback=foo
=> foo({"issues":...})

#4 Updated by Hai-Nam Nguyen over 4 years ago

If you come into this page by searching, since #12992 JSONP support is disabled by default.

#5 Updated by Toshi MARUYAMA over 4 years ago

  • Related to Feature #12992: Make JSONP support optional and disabled by default added

Also available in: Atom PDF