Hi,
Testing the tag with browser having different cookie settings reviles that it correctly embeds
sessionid in URLs even "the first time" something that the other method will not do and that is the reason for my interest.
If some is familiar with what controls this behavior then please clarify.
Best regards, -Stefan
Kris Schneider wrote:
Quoting Stef�n Baxter <[EMAIL PROTECTED]>:
Hi,
I'm new to JSTL and currently trying to adapt a project that I'm working on to it.
Am I right in assuming that standard.tag.el.core.UrlTag relies on it's own/JSTL functions to determine if sessionid needs to be embedded in theURL.
I see different behavior between it and HttpServletResponse.encodeURL().
Can someone please explain where the tag is gettings it's logic from?
According to the spec, <c:url> will not rewrite/encode an absolute URL. About the only thing this amounts to in the actual code is a check for the presence of the ":" character. If it's *not* there, then the URL will be rewritten/encoded with HttpServletResponse.encodeURL.
Best regards,
-Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
