Support CORS headers in the workbench and server

Description

It would be useful to support CORS headers to allow configurable cross-origin requests to the workbench from other domains.

This would either be in addition to support for JSONP or be a more configurable replacement for JSONP.

This was brought up by Barry Norton during discussion of on the mailing list:

http://sourceforge.net/mailarchive/message.php?msg_id=30543662

Environment

None

Activity

Show:

MarkH April 16, 2015 at 11:31 AM

Check out https://github.com/ebay/cors-filter. It has worked well for me with other things.

Former user October 10, 2014 at 5:13 PM

A note to the implementors…

From https://github.com/angular/angular.js/issues/3336: "I found the issue for a while now but I forgot post here a reply. EVERY response, even Error 500, must have the CORS headers attached. If the server doesn't attach the CORS headers to the Error 500 response then the XHR Object won't parse it, thus the XHR Object won't have any response body, status, or any other response data inside."

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Who's Looking?

Open Who's Looking?

Created February 28, 2013 at 11:49 PM
Updated April 21, 2016 at 9:37 PM
Resolved April 21, 2016 at 9:37 PM
Who's Looking?