Issue Details (XML | Word | Printable)

Key: JAVASERVERFACES_SPEC_PUBLIC-106
Type: Improvement Improvement
Status: Reopened Reopened
Priority: Major Major
Assignee: Unassigned
Reporter: martenlehmann
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
javaserverfaces-spec-public

add an external-attribut to url-rendering components

Created: 24/Aug/05 10:25 AM   Updated: 24/Jan/14 09:53 PM
Component/s: Components/Renderers
Affects Version/s: 2.0
Fix Version/s: 2.3

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All


Issuezilla Id: 106
Status Whiteboard:

cat2 javadoc sig size_medium importance_small

Tags:
Participants: Ed Burns, martenlehmann, rogerk and sheetalv


 Description  « Hide

I'd like to propose to add an external attribute to all components, that work
with url's. Usually, session-id's are stored in cookies. But if a browser
doesn't support cookies, the client has disabled it or the administrator
configured the java server to encode the cookie in the url instead of setting a
cookie by default [1], the session-id is encoded into the url where you don't
expect it. While it's surely wanted in url's of the same application context,
you will end up with an unexpected url at external addresses:

<h:outputLink value="http://www.yahoo.com"><h:outputText
value="yahoo"/></h:outputLink>

will generate:

<a href="http://www.yahoo.com;jsessionid=aoX0DYNXlII43PaHPx">yahoo</a>

An external="true" (false by default) could simply pass the url unchanged.

[1] You can do this in Resin if caucho.com with

<session-config>
<enable-cookies>false</enable-cookies>
</session-config>



Ed Burns added a comment - 27/Feb/06 01:54 PM

I think this is a good idea, especially given the javadoc for
ExternalContext.encodeResourceURL():

http://java.sun.com/javaee/javaserverfaces/1.2/docs/api/javax/faces/context/ExternalContext.html#encodeResourceURL(java.lang.String)


Ed Burns added a comment - 13/Mar/06 01:27 PM

Fix checked in.


Ed Burns added a comment - 24/Mar/06 12:40 PM

I didn't get to this one. Targeting for 2.0


Ed Burns added a comment - 20/Aug/08 08:26 PM
      • Issue 171 has been marked as a duplicate of this issue. ***

Ed Burns added a comment - 24/Sep/09 09:13 AM

Move to unscheduled target milestone


Ed Burns added a comment - 24/Nov/09 07:40 AM

Prepare to delete api subcomponent


Ed Burns added a comment - 04/Mar/10 12:30 PM

cat2


Ed Burns added a comment - 17/Mar/10 02:00 PM

javadoc


Ed Burns added a comment - 27/Apr/10 09:03 AM

sig change, new parameter on ExternalContext.encodeResourceURL.


Ed Burns added a comment - 15/May/10 07:54 AM

These are targeted at 2.1.


sheetalv added a comment - 10/Jun/10 11:42 AM

triage


Ed Burns added a comment - 24/Jun/10 01:32 PM

Change target milestone.


rogerk added a comment - 27/Oct/10 12:33 PM

triage