You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Georg Henzler (JIRA)" <ji...@apache.org> on 2017/06/08 21:44:18 UTC
[jira] [Commented] (SLING-6946) Make HC servlet send CORS header
Access-Control-Allow-Origin
[ https://issues.apache.org/jira/browse/SLING-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043498#comment-16043498 ]
Georg Henzler commented on SLING-6946:
--------------------------------------
Fixed in [r1798130|http://svn.apache.org/r1798130]
> Make HC servlet send CORS header Access-Control-Allow-Origin
> ------------------------------------------------------------
>
> Key: SLING-6946
> URL: https://issues.apache.org/jira/browse/SLING-6946
> Project: Sling
> Issue Type: Improvement
> Components: Health Check
> Reporter: Georg Henzler
> Assignee: Georg Henzler
>
> There is no reason why a HC servlet should not be allowed to called from a webpage that was served from another domain. Hence the header {{Access-Control-Allow-Origin}} shall be added with a default value {{*}} (configurable in case it is really needed, but allowing general access as default makes sense here).
> Concrete Use Case: A Jenkins HTML Report that aggregates HC results from multiple sling instances.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)