12 comments

  • 0

    I've found that, though it's not documented, the REST API supports JSONP.

    Try it: subsitute .json for .xml and add "?callback=mycallback." Voila, there it is. 

    It would be nice to hear that it's officially supported before I start relying on it however...

     

  • 0

    Hi Tim, we do support JSONP in /api/v1, but have currently removed it in /api/v2 until we further investigate security.  We'll let you know if we decide to officially support it.

  • 0

    Update: we will be supporting JSONP for public resources, e.g. retrieving public forums or public forum topics.  Outside of that we do not feel it's secure and will add CORS support for other cross-domain requests.

  • 0

    Hi.

    What's the latest on the CORS implementation mentioned above?

    LarsM

  • 0

    Hi Lars, nothing yet on CORS.

  • 0

    Thanks for quick feedback.

    Does that mean no support for cross-domain in API v2 in any shape or form at the moment?

    Still plan to add CORS in the end?

  • 0

    Hi Lars, that's correct, currently there's no support for cross-domain requests in API v2 at the moment.  We still do plan on adding CORS.

  • 0

    Hi Steven, any news on this?

  • 0

    Doesn't seem like GET requests to /api/v2/portal/search.json support JSONP :(

  • 0

    Why, oh why do you not provide CORS headers on some of the publicly accessible resources? Like:

    portal/search.json

    categories/{id}.json

    As CORS headers are present on forums, topics and so on, it seems that you forgot to put them also on search or categories...

    Please, be so kind and add them. API v2 is barely usable in current state

  • 0

    @Jacek: I've created a ticket on your behalf so that we can have an engineer review the CORS trouble you're having. Thanks for reaching out about this.

  • 0

    Thanks, Sean! I'm very glad and looking forward to hear from the engineers.

Please sign in to leave a comment.