On Wed, Oct 15, 2008 at 11:24 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: >> Seen that, and I think we should have a separate method here, as we >> don't want a session ID in Sling apps ;-) > > do we ? actually, what we say is "don't use HttpSessions". > > But if an application still wants to use an HttpSession (for whatever > reasons) and the client disables cookies (for whatever reasons), the > encodeURL method is the one described by the spec to be called to ensure > the URL bears the session ID.
Yes, but in my application, where I follow the REST pattern, I want to be sure there is no session ID included and still want the context path prepended. That's why I'd like a separate method to handle this use case. I could provide a patch (if I find some time ;-)) Regards, Alex -- Alexander Klimetschek [EMAIL PROTECTED]
