Project

General

Profile

Actions
Copy link

Feature #11469

closed

JSONP support

Added by Markus M about 13 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jean-Philippe Lang
Category:
REST API
Target version:
2.1.0
Start date:
Due date:
% Done:

0%

Estimated time:
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 jQueryClosed

Actions
Related to Redmine - Feature #13718: Accept dots in JSONP callbackClosedJean-Philippe Lang

Actions
Related to Redmine - Feature #12992: Make JSONP support optional and disabled by defaultClosedJean-Philippe Lang

Actions
Actions
Copy link
 #1

Updated by Etienne Massip about 13 years ago

  • Category set to REST API
Actions
Copy link
 #2

Updated by Jean-Philippe Lang almost 13 years ago

  • Assignee set to Jean-Philippe Lang
  • Target version set to 2.1.0
Actions
Copy link
 #3

Updated by Jean-Philippe Lang almost 13 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":...})
Actions
Copy link
 #4

Updated by Hai-Nam Nguyen over 10 years ago

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

Actions
Copy link
 #5

Updated by Toshi MARUYAMA over 10 years ago

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

Also available in: Atom PDF