axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal jayasinghe <>
Subject Re: Transport Level Session Management -- is this .NET interop Issue?
Date Fri, 03 Aug 2007 04:23:30 GMT
Hi Shalab ,
> Hello,
> I have a question about session management.
> My Axis client is a consumer of .NET service, I am noticing the
> following interoperability issue. The Service is returning Cookie as
> *Set-Cookie: ASP.NET_SessionId=cml1mh45lc3yzf55flravg45; path=/; HttpOnly*
According the the servlet specification it should send the JSESSIONID ,
anyway Axis2 has a way to deal with this as well. So when you send the
request set the following property into the option.
         Options options = new Options();

That will definitely solve the issue. You have to use Axis2 1.3 RC1 or
RC2 for this case.


> And this is not getting processed by Axis client.
> I have also created a test Axis service where I have enabled transport
> level sessions. The Cookie gets set here as:
> *Set-Cookie: JSESSIONID=0E2ACECB8CF2E5E91F55B5F8E6CEA150; Path=/axis2*
> In this case, Axis client is able to return back the sessionid to the
> Axis Service.
> Appreciate any input on how to work around this issue.
> Does Axis provide any API to inspect the incoming Cookies, and set
> outgoing Cookies explicitly?
> Thanks
> Shalab

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message