PK87799: WEB SERVICES CONSUMER CANNOT RETRIEVE MULTIPLE SET-COOKIE HEADERS ON THE RESPONSE FROM WEB SERVICES PRODUCER.

Fixes are available

APAR status

Closed as program error.

Error description

If there are multiple Set-Cookie headers in the HTTP response
from the Web Services producer not all Set-Cookie headers can be
retrieved  by the Web Services consumer. This can result in
unexpected behavior of the Web Services consumer application if
the application needs to read all the cookies in the
Set-Cookie headers returned.
.
The following is an example of how you can code a Web services
client to send and retrieve HTTP transport header values:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
topic=/com.ibm.websphere.express.doc/info/exp/ae/rwbs_transporth
eaderproperty.html
.
HashMap sendTransportHeaders=new HashMap();
sendTransportHeaders.put("Cookie","ClientAuthenticationToken=FFE
EBCC");
sendTransportHeaders.put("MyRequestHeader","MyRequestHeaderValue
");
((Stub)
portType)._setProperty(Constants.REQUEST_TRANSPORT_PROPERTIES,
sendTransportHeaders);
.
HashMap receiveTransportHeaders=new HashMap();
receiveTransportHeaders.put("Set-Cookie", null);
receiveTransportHeaders.put("MyResponseHeader", null);
((Stub)
portType)._setProperty(Constants.RESPONSE_TRANSPORT_PROPERTIES,
receiveTransportHeaders);
.
resultString=portType.echoString("Foo");
.
In case that there are multiple Set-Cookie headers in the HTTP
response from the Web Services producer only the first
Set-Cookie header will be retrieved and placed in the HashMap
by the Web Services consumer.

This problem was discovered in WebSphere Application Server
V6.1.0.17 release.

Local fix

```
N/A.
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  develpers of JAX-RPC using SET-COOKIE HTTP  *
*                  headers.                                    *
****************************************************************
* PROBLEM DESCRIPTION: The JAX-RPC client will only process    *
*                      the first SET-COOKIE header in a        *
*                      response.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If there are multiple SET-COOKIE HTTP headers in a response,
the client will only process the first occurrence of
a SET-COOKIE header.

Problem conclusion

The client code was changed to recognize the SET-COOKIE header
and allow for multiple occurences of the header.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.29 and 7.0.0.7.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK87799
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-02
Closed date
2009-07-17
Last modified date
2011-05-13

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PK89758

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK87799: WEB SERVICES CONSUMER CANNOT RETRIEVE MULTIPLE SET-COOKIE HEADERS ON THE RESPONSE FROM WEB SERVICES PRODUCER.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?