[
https://issues.apache.org/jira/browse/SLING-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-2706.
--------------------------------------
Resolution: Won't Fix
Assignee: Felix Meschberger
Since there already exists a good generic solution to the problem, this issue
will not get fixed.
> SlingHttpServletRequest.getScheme() should support offloaded SSL
> ----------------------------------------------------------------
>
> Key: SLING-2706
> URL: https://issues.apache.org/jira/browse/SLING-2706
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Jörg Hoh
> Assignee: Felix Meschberger
>
> Currently SlingHttpServletRequest.getScheme() only supports "https", if the
> HTTPS connection is terminated locally. But in many environments the https
> connection is terminated at a frontend layer (either loadbalancer or
> webserver), and then the requests are forwarded via http to sling (plus a
> special header indicating that this request was once received via https).
> Then .getScheme() won't return "https" anymore, but only "http".
> I would like to extend the SlingHttpServletRequestImpl and implement a
> .getScheme(), which considers a configurable HTTP header (e.g.
> "X-frontend-ssl") of the request. If this value is set, then .getScheme()
> will return "https".
> I want to make this header name configurable via OSGI, but I haven't found
> any good place yet. Any ideas?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
