You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/05/07 01:00:22 UTC
[jira] Updated: (CONTINUUM-1737) Https proxy in front of jetty
doesn't work very well.
[ http://jira.codehaus.org/browse/CONTINUUM-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1737:
------------------------------------
Assignee: (was: Martin van den Bemt)
Fix Version/s: 1.x
is this a problem in jetty5 (embedded in 1.1), or all versions (since we default to jetty6 in 1.2, and primarily distribute as a webapp)?
> Https proxy in front of jetty doesn't work very well.
> -----------------------------------------------------
>
> Key: CONTINUUM-1737
> URL: http://jira.codehaus.org/browse/CONTINUUM-1737
> Project: Continuum
> Issue Type: Improvement
> Components: Web - Configuration
> Reporter: Martin van den Bemt
> Fix For: 1.x
>
>
> It is not a bug in continuum, but in Jetty. The continuum system relies heavily on sendRedirects. Jetty however makes the Location http header an absolute url instead of a relative url. The simple fix is to add a filter to override sendRedirect. I made this filter (I have this fix available), but before it could end up in continuum it is best to have a more generic solution or make it configurable to use to filter or not (in case of issues in other containers, which I haven't tested yet).
> Feedback welcome.
> Not asking for a fix, I will provide it and will use this issue to track it and also add documentation on how to set this all up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira