You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Ilya Obshadko (JIRA)" <ji...@apache.org> on 2014/02/20 01:16:20 UTC
[jira] [Created] (TAP5-2291) respect X-Forwarded-Proto HTTP header
and probably other X-Forwarded-* headers as well
Ilya Obshadko created TAP5-2291:
-----------------------------------
Summary: respect X-Forwarded-Proto HTTP header and probably other X-Forwarded-* headers as well
Key: TAP5-2291
URL: https://issues.apache.org/jira/browse/TAP5-2291
Project: Tapestry 5
Issue Type: Wish
Components: tapestry-core
Affects Versions: 5.3.7
Reporter: Ilya Obshadko
Use case: we need to correctly handle scenarios when Tapestry acts as a plain (unsecured) HTTP backend behind HTTPS frontend. In such situations all links, either formed by PageLink/EventLink/ActionLink components, or by directly using PageRenderLinkSource, should contain correct port and protocol.
I've created a basic support for X-Forwarded-Proto header in my project. The solution is described here: https://gist.github.com/xfyre/9104238
It might be a good idea to incorporate support for X-Forwarded-Proto header into Tapestry itself. Otherwise we need to rely on servlet container to provide correct request information and it doesn't always work as expected.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)