PK95736: ODR/PROXY DOES NOT AUTOMATICALLY REWRITE 302 RESPONSE LOCATION HEADER FOR GSC ROUTING RULES.

Fixes are available

APAR status

Closed as program error.

Error description

When generic server cluster (GSC) routing rules are defined,
proxy is not able to automatically correct the location header
in 302 responses returned from servers.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: When 302 responses are returned from    *
*                      the GSC server, the proxy could not     *
*                      correct bad value in the location       *
*                      header.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Proxy server does not have the ability to auto-correct some
bad links in the location header returned from generic server
cluster (GSC). And this causes bad redirect link in the
browsers.

Problem conclusion

In this fix, following proxy custom property is created:

Property name: "http.auto.redirect.correction"
Value: string value of [none|gsc|managed|all]

default value of the property is "gsc". So by default, for the
302 responses returned from the generic server cluster, the
proxy server will try to correct the value in the location
header.

Note: junction rewrite rule will override this custom property.


The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.29 and 7.0.0.9.  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
PK95736
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-09-09
Closed date
2009-11-12
Last modified date
2009-11-12

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
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:
28 December 2021

Tips

PK95736: ODR/PROXY DOES NOT AUTOMATICALLY REWRITE 302 RESPONSE LOCATION HEADER FOR GSC ROUTING RULES.

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?