[
https://issues.apache.org/jira/browse/FELIX-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Hoh updated FELIX-4920:
----------------------------
Attachment: sslfilterDoesNotPreserverUriFragment.patch
A patch including the testcase to demonstrate the behaviour plus a fix. It
basically changes the handling to use a URI instead of a URL.
> sslfilter does not preserve fragment in redirect
> ------------------------------------------------
>
> Key: FELIX-4920
> URL: https://issues.apache.org/jira/browse/FELIX-4920
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
> Affects Versions: http-sslfilter-1.0.0
> Reporter: Jörg Hoh
> Attachments: sslfilterDoesNotPreserverUriFragment.patch
>
>
> I have an application which behaves like this when sslfilter-0.0.1 is
> installed:
> $ curl -v -u admin:admin -H "X-Forwarded-SSL:on"
> "http://localhost/bin/command?cmd=open&path=/page";
> GET /bin/command?cmd=open&path=/page HTTP/1.1
> ...
> < HTTP/1.1 302 Found
> < Date: Mon, 08 Jun 2015 19:10:33 GMT
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < Location: /cf#/page.html
> Then I deployed sslfilter-1.0.0
> $ curl -v -u admin:admin -H "X-Forwarded-SSL:on"
> "http://localhost/bin/command?cmd=open&path=/page";
> ...
> GET /bin/command?cmd=open&path=/page HTTP/1.1
> ...
> < HTTP/1.1 302 Found
> < Date: Mon, 08 Jun 2015 19:10:06 GMT
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < Location: https://localhost/cf
> As you can see, the protocol is changed accordingly (that's why I wanted to
> update), but the fragment part of the location header (#/page.html) is not
> preserved.
> I tracked it down to FELIX-4420, where the rewriting of the location was
> implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
