PI35277: SERVER NOT RESPONDING TO CONTINUE MESSAGE AS EXPECTED

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.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

• the new RFC specification says
  that 100-Continue response messages should not contain the
  content-length header. While we don't guarantee changes based
  on a new spec, we will in this case. Page 117 of 118
  
  This is what the specification states on section 3.3.2:
  http://tools.ietf.org/html/rfc7230#section-3.3.2
  
  A server MUST NOT send a Content-Length header field in any
  response with a status code of 1xx (Informational) or 204 (No
  Content).
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Version    *
  *                  8.5.5 Full Profile and Liberty Profile      *
  *                  users                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Content-Length header present on        *
  *                      response messages with status of 1xx    *
  *                      or 204                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The response to a request with a "Expect: 100-continue" header
  contains a content-length header as shown in the example below:
  > POST /testRequest HTTP/1.1
  > Host: localhost
  > Accept: */*
  > Content-Length: 2178
  > Content-Type: application/x-www-form-urlencoded
  > Expect: 100-continue
  >
  < HTTP/1.1 100 Continue
  < Content-Length: 0
  Current behavior is not in accordance to RFC7230 which states
  in section 3.3.2:
  A server MUST NOT send a Content-Length header field in any
  response with a status code of 1xx (Informational) or 204 (No
  Content).
  

Problem conclusion

• The HTTP Channel will now prevent sending the Content-Length
  header on response messages with a informational status of 1xx
  or 204.
  
  A new custom property was added to the HTTP Channel to enable
  this new behavior. The property name is:
  "RemoveCLHeaderInTempStatusRespRFC7230compat" with a possible
  value of "true" or "false", with the default being "false".
  
  An HTTP Channel custom property can be set like this:
  
  http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.i
  bm.websphere.nd.doc/ae/rrun_chain_httpcustom.html?cp=SSAW57_8.5.
  5%2F1-18-6-409&lang=en
  
  Please note: the instructions are for v8.5.5, but the same
  instructions apply to all versions of WebSphere Application
  Server Full Profile
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.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 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

• R850 PSY

     UP