Project

General

Profile

Actions

Task #6781

closed

Enable content proxying on the host running MetacatUI

Added by Chris Jones over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
06/18/2015
Due date:
% Done:

0%

Estimated time:

Description

MetacatUI has been built up to make cross-origin calls to various services, particularly some of the DataONE search, node, and account services. However, Lauren pointed out that IE8 and IE9 don't support CORS headers, and so these cross-origin requests fail. As an alternative, set up a proxy service that will be an intermediate server between the client and the origin server (like the CN). After discussion with Lauren and Ben, we thought that setting up apache mod_proxy (in reverse proxy mode) in conjunction with mod_rewrite would enable pass-through functionality. For instance, a call to
https://search.test.dataone.org/cn/v1/accounts
will be proxied to
https://cn.dataone.org/cn/v1/accounts
and the Response would be sent back to the client. The MetacatUI client will still handle both XML and JSON responses.

Our second approach would be to write a custom servlet for the proxying that would run on the server hosting the MetacatUI code.


Related issues

Related to MetacatUI - Task #6780: Cross-origin resource sharing issues in IE and some versions of FFResolvedLauren Walker06/09/2015

Actions
Actions

Also available in: Atom PDF