Peter Renstroem commented on Feb 27, 2013

Re: Manage CORS in WebSphere Portal

Hmm, my tags got stripped but:

init-param

param-name com.ibm.portal.cors.domain.list /param-name

param-value * /param-value

/init-param

init-param

param-name com.ibm.portal.cors.domain.*.maxage /param-name

param-value 99999 /param-value

/init-param

Peter Renstroem commented on Feb 27, 2013

Re: Manage CORS in WebSphere Portal

Could you give an example of how to add multiple values to com.ibm.portal.cors.domain.fulldomainname.methods? Are they separated by commas, spaces or their own tags?

Furhermore, is it possible to use wildcards? More specifically "*". Kinda like so:

com.ibm.portal.cors.domain.list

*

com.ibm.portal.cors.domain.*.maxage

99999

Peter Renstroem commented on Feb 26, 2013

Re: Manage CORS in WebSphere Portal

Is it possible to completely disable this feature? This stuff belongs on the HTTP server (Access-Control-Allow-Origin much?), not in WebSphere Portal. As of now, it's a pain to have the HTTP server on a different machine from WebSphere Portal. And more often than not, the actual machine hostname isn't the same as the external domain name you access it by.