Re: [jetty-users] Changes Between 7.0.2 and 7.4.4

[Greg Wilkins <gregw@xxxxxxxxxxx>]

Jetty is a bit lazy and doesn't check by default what is lazy and what
is not.   Try turning on

    public void setCheckingRemoteSessionIdEncoding(boolean remote);

on the session manager, so that it will look at the hostname you are
redirecting to and if it does not match the server host, then it is
considered remote and the jsessionid will not be encoded.

cheers


On 19 July 2011 11:08, Mack Gerhardt <mack@xxxxxxxxxxxxxx> wrote:
> Is this the correct behavior, because this is the initial request into a
> webapp, the server doesnt know if cookies are enabled, and the first request
> into the server is doing the redirect. I do have session cookies enabled on
> the server. I think the server just thinks cookies are not enabled since a
> request came in with no cookies, and is being redirected immediately. I am
> doing a redirect to a remote server and the JSESSIONID makes no sense to
> encode on the url. But I would still like to enable session cookies within
> the webapp. Any workarounds?
> thanks
>
> On Mon, Jul 18, 2011 at 8:41 PM, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
>>
>> Mack,
>>
>> This was a fix to bring jetty in line with the correct behaviour.
>> Send redirect now encodes the URL if there was no session cookie
>> present.   If you don't want URL session tracking then you can turn it
>> off by setting a setSessionIdPathParameterName of null on the session
>> manager.
>>
>> you can see the changes made to Jetty at
>>
>> http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/tree/VERSION.txt
>>
>> and cross reference details with bugzilla/jira
>>
>> In this case the bug fixed was http://jira.codehaus.org/browse/JETTY-1146
>>
>> regards
>>
>>
>> On 16 July 2011 13:44, Mack Gerhardt <mack@xxxxxxxxxxxxxx> wrote:
>> > I noticed that when I do a sendRedirect from a filter with the following
>> > call
>> > response.sendRedirect(IM_URL);
>> > that when I do redirect to a url to a different domain it adds a
>> > jsessionid
>> > to the redirect. Before this was not the case. Below is a header dump. I
>> > have noticed that we also have a blackberry application that used to
>> > make
>> > http calls to the server, with 7.0.2 it worked correctly, in 7.4.4 it is
>> > broken, I havent had time yet to wireshark it to find the differences.
>> > Is
>> > there a list of changes to the http handling.
>> > HTTP/1.1 302 Found
>> > Set-Cookie: JSESSIONID=4plrq09v5o8d115m079wftf14;Path=/
>> > Expires: Thu, 01 Jan 1970 00:00:00 GMT
>> > Location:
>> > http://localhost/im/index.shtml;jsessionid=4plrq09v5o8d115m079wftf14?
>> > Content-Length: 0
>> > Server: Jetty(7.4.4.v20110707)
>> > Thanks
>> > Max
>> >
>> >
>> > _______________________________________________
>> > jetty-users mailing list
>> > jetty-users@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/jetty-users
>> >
>> >
>> _______________________________________________
>> jetty-users mailing list
>> jetty-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>