DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33355>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33355

           Summary: computeURLWithCharEncoding doesn't encodes the & created
                    by the response.encudeURL call
           Product: Struts
           Version: 1.2.6 Beta
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: trivial
          Priority: P4
         Component: Custom Tags
        AssignedTo: dev@struts.apache.org
        ReportedBy: [EMAIL PROTECTED]


When the emcopdeURL called from the TagUtils computeURLWithCharEncoding  and 
only one parameter exists then encodeURL insert a & sign to separate the old 
parameter from the sessionid.
example:
http://s.ss.s/CustomerlistActoion%3Flistid=1 
encoded as
http://s.ss.s/CustomerlistActoion%3Fjsessionid=111&listid=1
But the usage of & signs is invalid in the PCDATA encoded href attribute. The 
usage of th &amp; is allowed here.

There have to be encoded the URL to PCDATA after the calling of encodeURL to 
avoid html validation errors.
The current code first creates a URL like 
http://s.ss.s/CustomerlistActoion%3Flistid=1&amp;bubu=bubu2
The servlet engina parse it as :
Base: "http://s.ss.s/CustomerlistActoion"; 
parameter1 =  "listid" 
value of parameter1 = 1&amp;bubu=bubu2
The good solution:
Step1:Create an urlencoded url wiht usage of & as separators.
Step2:Calling of response.encodeURL
Step3: Call the PCDATA encoding to whole url.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to