Bug 111353 - RedirectSignal fails with relative URLs
RedirectSignal fails with relative URLs
Status: CLOSED WONTFIX
Product: Red Hat Web Application Framework
Classification: Retired
Component: other (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-12-02 10:32 EST by Matthew Booth
Modified: 2007-06-17 18:04 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-17 18:04:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Matthew Booth 2003-12-02 10:32:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Gecko/20031026 Firebird/0.7

Description of problem:
I know this it is against the relevant RFC to send a relative
redirect, however this is an exceptionally useful thing to have. I had
always assumed that RedirectSignal rewrote relative redirects, but
this error:

java.lang.IllegalStateException: The URL is relative and won't
dispatch correctly under some servlet containers; the URL is 'index.jsp'
	at com.arsdigita.util.Assert.assertTrue(Assert.java(Compiled Code))
	at com.arsdigita.web.RedirectSignal.(RedirectSignal.java:65)

seems to suggest that it didn't.

Given that this code used to work in practise, breaking it now seems a
little unhelpful.

RedirectSignal should trap relative URLs and rewrite them to be full
URLS based on the context of the current request. Otherwise this exact
code will have to be duplicated everywhere a relative redirect is desired.

As it stands this is a regression.

Version-Release number of selected component (if applicable):
Rickshaw

Note You need to log in before you can comment on or make changes to this bug.