PI21655: 404 RETURNED WHEN ATTEMPTING TO BROWSE A MEMBER OF A PDS DATASET USING MVSDS

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Various mod_mvsds fixes:
  
  When browsing an PDS dataset (with MVSIndexes ON) and
  attempting to view a member with a # sign in the name, a 404 is
  returned to the browser.
  
  If a PDS dataset is enclosed in quotes (User ID is
  included), the wrong content type can be set, resulting in
  unexpected behavior such as download dialogues.
  
  Some binary file formats, such as PDF, are malformed when
  served through mod_mvsds.
  

Local fix

• Browse the member directly and replace the # sign with %23.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM HTTP Server users of the mod_mvsds      *
  *                  module running on z/OS.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: 404 responses for requests for          *
  *                      partitioned dataset member names        *
  *                      containing special characters.          *
  *                      Incorrect content type being set.       *
  *                      Data corruption for binary content.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Requests for partition dataset members with names containing
  '$', '#', or '@' return a 404.
  The HTTP server may not match the correct file suffix to a
  MIME type, causing the Content-Type: header to be incorrectly
  set.
  Binary type files were not being read in binary mode causing
  x'15' characters to be inserted into the output.
  

Problem conclusion

• The URLs will be properly escaped to handle the special
  characters properly.  The trailing quote character will be
  removed before matching MIME type suffixes. Binary content
  type files will be correctly read in binary mode.
  The directive MvsdsDefaultTextType is added to allow the
  customer to configure the default text content type to be used
  when no MIME type match is made on a dataset. Default is
  text/plain.
  

Temporary fix

Comments

APAR Information

• 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

  WAS IHS ZOS

• Fixed component ID

  5655I3510

Applicable component levels

• R850 PSY

     UP