[SLING-2251] RedirectServlet should create relative Location headers as often as possible

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Servlets Get 2.1.2
• Fix Version/s: Servlets Get 2.1.4
• Component/s: Servlets
• Assignee: Felix Meschberger
• Reporter: Alexander Klimetschek
• Created: 19/Oct/11 13:00
• Updated: 26/Feb/15 23:57
• Resolved: 30/Jan/12 12:56

Description

SLING-1965 (more specifically http://svn.apache.org/viewvc?view=revision&revision=903175 ) changed the redirect servlet so that it always generates an absolute location header. The issue does not give much reasoning for that.

The problem is that this breaks cases where a Sling server is run behind a proxy (which does not or cannot rewrite the Location header), as the redirect ("http://localhost:8080/some/path") might not match the externally visible domain (e.g. "https://my.domain.com"). Also, the schema is fixed (e.g. might switch external https back to http).

A solution would be to generate absolute URLs only if a resource resolver mapping (/etc/map) includes an explicit domain and thus generates an absolute URL. For all other cases, relative URLs should be generated. AFAICS, this was the case before SLING-1965.

Issue Links

• is related to: SLING-3374 Overlay sendRedirect to set relative Location header