PK78371: THE QUERY STRING IS NOT INCLUDED DURING THE DISPATCHER FORWARD TO A WELCOME FILE

Fixes are available

APAR status

Closed as program error.

Error description

The passing URL variables to the welcome-file without
calling out the welcome file does not maintain its values.

For example, if the web.xml file has the welcome file defined as
follow:
 <welcome-file-list id="WelcomeFileList_1034013110672">
     <welcome-file>index.cfm</welcome-file>
 </welcome-file-list>

For the request URL "hostname/?a=1" the content of index.cfm is
only displayed, but it is un-aware of the variable "a".

Local fix

The workaround is to add the attribute redirectToWelcomeFile in
the web-ibm-ext.xmi file:

<fileServingAttributes xmi:id="YourID_1"
name="redirectToWelcomeFile" value="true"/>

This will redirect to welcome file (instead of forward) and
will contain the original query string of the request.

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server version    *
*                  6.1 and 7.0 users who pass a query string   *
*                  to welcome files.                           *
****************************************************************
* PROBLEM DESCRIPTION: When a request is forwarded to a        *
*                      welcome file, the query string is not   *
*                      available via request.getQueryString(). *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Typically a request is forwarded to a welcome file when that
request is initially to the context root of the application.
If a query string is part of an initial request, it is not
available to the welcome file via request.getQueryString().
However, it is available via the attribute
"javax.servlet.forward.query_string".

For example, a request to a context root will be forwarded to
a welcome file
http://localhost:port/Context_Root/?param=value

in the welcome file:

request.getQueryString()
        returns null
request.getAttribute("javax.servlet.forward.query_string")
        returns param=value

Problem conclusion

The WebContainer was modified to make the original query
string available via request.getQueryString() to a welcome
file.
The following WebContainer custom property must set to true
for this to work:

com.ibm.ws.webcontainer.provideQStringToWelcomeFile =
true/false(default)

Please refer to the following technote for instructions on
enabling WebContainer custom properties:
http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.25 and 7.0.0.5.  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
PK78371
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-09
Closed date
2009-03-25
Last modified date
2009-04-01

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

PK78371: THE QUERY STRING IS NOT INCLUDED DURING THE DISPATCHER FORWARD TO A WELCOME FILE

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?