IY50754: WEBSEAL RETURNS BAD REQUEST 0X38CF0424 TO LARGE UTF-8 POST

APAR status

• Closed as program error.

Error description

• Environment: Access Manager WebSEAL 4.1 FP06
  When posting a large amount of UTF-8 data, WebSEAL can return
  Bad Request 0x38cf0424.  See APAR IY50332 for details.
  

Local fix

Problem summary

• WebSEAL can return an incorrect 400-error if dynurls are
  enabled and it receives a big UTF-8 POST.
  

Problem conclusion

• Fixed in 4.1-AWS-0008LA.
  Dynurl processing causes uridecode to get called with
  only N<M packets of an M packet message having been read.
  If the message is a UTF-8 POST, then the bytes of a
  multibyte UTF-8 character could have been split across
  the end of the Nth packet, causing a 400-error to be
  returned because there was a bad UTF-8 character (just
  the first half).  The fix detects this condition, zeros
  out the bad UTF-8 byte(s) -- thereby moving the end of
  the buffer up to contain only good UTF-8 characters --
  and does not return an error.  The handling of an end-of-
  buffer in the middle of a %uhhhh or %hh%hh encoding was
  also corrected - no error is reported now.
  

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

  ACCESS MGR WEBS

• Fixed component ID

  5724C0811

Applicable component levels

• R410 PSY

     UP