Project

General

Profile

Actions

Feature #11469

closed

JSONP support

Feature #11469: JSONP support

Added by Markus M over 14 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Category:
REST API
Target version:
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 3 (0 open — 3 closed)

Related to Redmine - Defect #10761: Rest API JSON response can not be parsed by jQueryClosedActions
Related to Redmine - Feature #13718: Accept dots in JSONP callbackClosedJean-Philippe LangActions
Related to Redmine - Feature #12992: Make JSONP support optional and disabled by defaultClosedJean-Philippe LangActions

Updated by Etienne Massip over 14 years ago Actions #1

  • Category set to REST API

Updated by Jean-Philippe Lang over 14 years ago Actions #2

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

Updated by Jean-Philippe Lang over 14 years ago Actions #3

  • 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":...})

Updated by Hai-Nam Nguyen almost 12 years ago Actions #4

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

Updated by Toshi MARUYAMA almost 12 years ago Actions #5

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

Also available in: PDF Atom