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=36774>. 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=36774 ------- Additional Comments From [EMAIL PROTECTED] 2005-11-07 23:14 ------- Niall, Thanks for the reply - I was looking to the HTML specs, too, to see if there was a requirement one way or the other. I believe my problem came about by way of some JavaScript that I inherited that was simply using a split() function looking for an ampersand as the separator for URL params. I can make adjustments as I find them. If you were able to supply a switch on the <html:link> tag, that might be helpful in allowing time fix problems, especially if I'm dealing with vendor-supplied JavaScript that might take some time to get fixed. If you'd rather not add the tag parameter, we can probably close this bug report. Thanks, Bob (In reply to comment #0) > I recently upgraded from Struts 1.1 to Struts 1.2.7 and use the feature of the > <html:link> tag to get multiple params from a Map interface. The URL is now > encoding the ampersands that separate the params. > emplRcd=0&seq=0&employeeId=1234567890 > when the output should be > emplRcd=0&seq=0&employeeId=1234567890 > I found that the TagUtils.computeURLWithCharEncoding() method was passing a > hard-coded value of "true" as the encodeSeparator method param. By changing > this to "false", the ampersands no longer get encoded. (In reply to comment #2) > The HTML 4.01 specification recommends encoding ampersand values because > otherwise it can conflict "with its use in SGML attribute values to delimit > character entity references": > http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.2 > Struts has had this behaviour since version 1.1 and I don't envisage that we > would change the default behaviour. However if you could explain why/how this > is causing you a problem then perhaps we could add an attribute to the LinkTag > that enables this behaviour to be switched off. Something like: > <html:link href="..." encodeSeparator="false" /> (In reply to comment #2) > The HTML 4.01 specification recommends encoding ampersand values because > otherwise it can conflict "with its use in SGML attribute values to delimit > character entity references": > http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.2 > Struts has had this behaviour since version 1.1 and I don't envisage that we > would change the default behaviour. However if you could explain why/how this > is causing you a problem then perhaps we could add an attribute to the LinkTag > that enables this behaviour to be switched off. Something like: > <html:link href="..." encodeSeparator="false" /> (In reply to comment #2) > The HTML 4.01 specification recommends encoding ampersand values because > otherwise it can conflict "with its use in SGML attribute values to delimit > character entity references": > http://www.w3.org/TR/html4/appendix/notes.html#h-B.2.2 > Struts has had this behaviour since version 1.1 and I don't envisage that we > would change the default behaviour. However if you could explain why/how this > is causing you a problem then perhaps we could add an attribute to the LinkTag > that enables this behaviour to be switched off. Something like: > <html:link href="..." encodeSeparator="false" /> -- 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]
