PK36307: PROBLEM WITH SENDING LARGE PDF FILES WHEN THE HOST APPLICATION SETS THE ACCEPT-RANGES BYTES HEADER.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The Customer has set accept ranges to NONE in the httpd.conf
  file. The problem occurs when a request comes in for a
  large .pdf file, thru the http server/plugin, the websphere
  app sets the accept ranges header, and starts sending the
  file. HTTPD_write had stream errno  140 errno2: 74520442
  JRSocketRstReceived. The same request is sent back in from
  the client, with a set of range bytes. The Websphere app
  ignores the ranges and starts sending the complete file
  again, which causes the adobe to issue 'The flle is damaged
  and could not be repaired' error message.
  there is no problem with the same flow when the request
  is made directly to the application thru the transport.
  

Local fix

• If possible issue the request thru the WebSphere Transport.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Any user of the HTTP Server for z/OS that    *
  *                 serves PDF files from CGIs or GWAPIs.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The customer is serving a PDF file from *
  *                      the WebSphere Application Server and    *
  *                      instead of the PDF file being displayed *
  *                      the following message is displayed:     *
  *                      ERROR: ihs390WAS50HttpPluugin:          *
  *                      cb_write_body: Failed to write the      *
  *                      response to the client 1.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Adobe Acrobat browser plugin routinely sends a -connection
  reset- when receiving a large PDF file.  Then re-sends the same
  request with a range header.  This is a method that Adobe uses
  to quickly display data to the client.  Most of the time this
  method works fine, but in this case the customer module did not
  handle the range headers.  The customer module ignored the range
  header and resent the entire PDF file. Because the range header
  switch was set the HTTP Server set the response code to 206
  partial content.  The 206 caused the Adobe plugin to expect the
  data in the range format with delimiters which are not present
  in a full send of a PDF file.
  

Problem conclusion

• Changed the code of the HTTP Server for z/OS to not set the 206
  partial content response if range header switch is set and the
  response is from a customer module.
  
  The following COMPID is affected by these changes:
  
  5697D4300 HTTP Server for z/OS  Version 5
  
  PTF07B
  The code changes are stored in CMVC under defect PK36307.
  
  * Cross Reference between External and Internal Names
  

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:

Modules/Macros

• IMWSDMDR IMWSRNGE
  

Fix information

• Fixed component name

  DGW/WAS OS/390

• Fixed component ID

  5697D4300

Applicable component levels

• R530 PSY UK21495

     UP07/01/26 P F701

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.