You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org> on 2004/10/26 08:34:43 UTC
[jira] Created: (AXISCPP-226) Provide session handling suport (cookies)
Provide session handling suport (cookies)
-----------------------------------------
Key: AXISCPP-226
URL: http://issues.apache.org/jira/browse/AXISCPP-226
Project: Axis-C++
Type: Improvement
Components: Transport (Client), Transport (Server)
Environment: All platforms
Reporter: Samisa Abeysinghe
Assigned to: Samisa Abeysinghe
Fix For: 1.4 Alpha
There is no mechanism to handle sessions.
Provide caapability to deal with cookies; first for the client; then if possible for server
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-226) Provide session handling suport (cookies)
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-226?page=comments#action_54870 ]
Samisa Abeysinghe commented on AXISCPP-226:
-------------------------------------------
>From http://www.fawcette.com/javapro/2003_04/online/wsdl_kjones_04_29_03/default_pf.aspx :
There is no standard way of managing session in a Web service, although there are two accepted techniques. The first is to rely on HTTP and use HTTP cookies. The second, and probably the most significant way, is to use SOAP headers. Axis Java lets developers do both.
Using HTTP managed sessions is the default in Axis Java.
This will cause the Axis framework to generate a set-cookie header:
Set-Cookie:
JSESSIONID=49EBBB19A1B2F8D10EE075F6F14CB8C9;
Path=/axissessions
A client needs to return this Cookie in a Cookie header to maintain the session.
The header looks like this:
Cookie:
JSESSIONID=49EBBB19A1B2F8D10EE075F6F14CB8C9
Using SOAP headers to carry the session id.
Axis Java comes with a handler called org.apache.axis.handlers.SimpleSessionHandler that provides SOAP header based session management.
> Provide session handling suport (cookies)
> -----------------------------------------
>
> Key: AXISCPP-226
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-226
> Project: Axis-C++
> Type: Improvement
> Components: Transport (Client), Transport (Server)
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Fix For: 1.4 Alpha
>
> There is no mechanism to handle sessions.
> Provide caapability to deal with cookies; first for the client; then if possible for server
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-226) Provide session handling suport (cookies)
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-226?page=history ]
Samisa Abeysinghe closed AXISCPP-226:
-------------------------------------
Related bug, AXISCPP-254 was resolved. Testing so far on Cookie based sessions revealed no problems.
> Provide session handling suport (cookies)
> -----------------------------------------
>
> Key: AXISCPP-226
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-226
> Project: Axis-C++
> Type: Improvement
> Components: Transport (Client)
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Fix For: 1.4 Alpha
>
> There is no mechanism to handle sessions.
> Provide caapability to deal with cookies; first for the client; then if possible for server
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXISCPP-226) Provide session handling suport (cookies)
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-226?page=history ]
Samisa Abeysinghe resolved AXISCPP-226:
---------------------------------------
Resolution: Fixed
Client side Cookie based session handling was implemented. Now the client is capable of tracking 'Set-Cookie' HTTP header sent with the service response and set the 'Cookie' HTTP header in the outgoing requests accordingly.
The implementation of Cookie based session handling is identicle to that of Axis Java.
A sample was also written to explain what needs to be done to use sessions as well as to test the behaviour. The sample is in samples/client/session/cookie and works with an Axis Java service.
There is a readme.txt file in samples/client/session/cookie folder that explains what the user needs to do to get Cookie based sessions working. (It is as simple as calling setMaintainSession(true) on the Stub object)
> Provide session handling suport (cookies)
> -----------------------------------------
>
> Key: AXISCPP-226
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-226
> Project: Axis-C++
> Type: Improvement
> Components: Transport (Client)
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Fix For: 1.4 Alpha
>
> There is no mechanism to handle sessions.
> Provide caapability to deal with cookies; first for the client; then if possible for server
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-226) Provide session handling suport (cookies)
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-226?page=history ]
Samisa Abeysinghe updated AXISCPP-226:
--------------------------------------
Component: (was: Transport (Server))
Server side Cookie based session need to be implemented seperately, and most probably for in 1.5.
> Provide session handling suport (cookies)
> -----------------------------------------
>
> Key: AXISCPP-226
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-226
> Project: Axis-C++
> Type: Improvement
> Components: Transport (Client)
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Fix For: 1.4 Alpha
>
> There is no mechanism to handle sessions.
> Provide caapability to deal with cookies; first for the client; then if possible for server
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-226) Provide session handling suport (cookies)
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXISCPP-226?page=comments#action_54871 ]
Samisa Abeysinghe commented on AXISCPP-226:
-------------------------------------------
>From http://wp.netscape.com/newsref/std/cookie_spec.html :
Set-Cookie: NAME=VALUE; expires=DATE; path=PATH; domain=DOMAIN_NAME; secure
Cookie: NAME1=OPAQUE_STRING1; NAME2=OPAQUE_STRING2 ...
> Provide session handling suport (cookies)
> -----------------------------------------
>
> Key: AXISCPP-226
> URL: http://nagoya.apache.org/jira/browse/AXISCPP-226
> Project: Axis-C++
> Type: Improvement
> Components: Transport (Client), Transport (Server)
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Fix For: 1.4 Alpha
>
> There is no mechanism to handle sessions.
> Provide caapability to deal with cookies; first for the client; then if possible for server
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira