IY71987: WEBSEAL DOES NOT FORWARD ERROR 503

5.1.0-TIV-TAM-IF0043-WIN
5.1.0-TIV-TAM-IF0043-LIN
5.1.0-TIV-TAM-IF0043-PPC
5.1.0-TIV-TAM-IF0043-SOL
5.1.0-TIV-TAM-IF0043-S390
5.1.0-TIV-TAM-IF0043-HP
5.1.0-TIV-TAM-IF0043-AIX
Tivoli Access Manager for e-Business WebSEAL, Patch 5.1.0-TIV-AWS-FP0039
Tivoli Access Manager for e-Business WebSEAL, Patch 5.1.0-TIV-AWS-FP0040
Tivoli Access Manager for e-Business WebSEAL, Patch 5.1.0-TIV-AWS-FP0041
Tivoli Access Manager for e-Business WebSEAL, Patch 5.1.0-TIV-AWS-FP0042

APAR status

• Closed as documentation error.

Error description

• Platforms:
  TAMeb 5.1 FP11
  aix 520 ml03 ,W2K server sp04
  Problem description:
  WebSeal 5.1 ( also verified with latest FP 13 )
  does not forward the 503 error code
  and translate it with  500 Internal Server Error.
  This is nt the case wth TAM 4.1 that correctly
  propagates the error 503 code.
  What is also interesting ( and I think also wrong ) is that
  WebSEAL 5.1 also set the back-end server as  "lost contact with
  back-end ...."  as soon as it receives 503 from the back-end
  and immediately later it recovers !!!
  this can bee seen in the webseald_message.log
  I've replicated the problem with TAM 5.1
  and I've also found that TAM 4.1 is able to propagate correctly
  the 503
  error code from the back-end to the browser
  TAM 5.1
  https://msilipo.tam2000.com:444/was-namibia/fammever/sendmecode?
  retcode=503
  GET /was-namibia/fammever/sendmecode?retcode=503 HTTP/1.1
  Host: msilipo.tam2000.com:444
  User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
  rv:1.7.6)
  Gecko/20050317 Firefox/1.0.2
  Accept:
  text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,t
  ext/plain;q=0.8,image/png,*/*;q=0.5
  Accept-Language: en-us,en;q=0.5
  Accept-Encoding: gzip,deflate
  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
  Keep-Alive: 300
  Connection: keep-alive
  Authorization: Basic cGlwcG86bWFkcmlkMDA=
  HTTP/1.x 500 Internal Server Error
  Date: Wed, 04 May 2005 18:28:22 GMT
  Server: WebSEAL/5.1.0.0 (Build 031024)
  Cache-Control: no-cache
  Pragma: no-cache
  Content-Length: 1615
  p3p: CP="NON CUR OTPi OUR NOR UNI"
  Content-Type: text/html
  TAM 4.1
  https://watermelon.secsupport.com/was-namibia/fammever/sendmecod
  e?retcode=503
  GET /was-namibia/fammever/sendmecode?retcode=503 HTTP/1.1
  Host: watermelon.secsupport.com
  User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
  rv:1.7.6)
  Gecko/20050317 Firefox/1.0.2
  Accept:
  text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,t
  ext/plain;q=0.8,image/png,*/*;q=0.5
  Accept-Language: en-us,en;q=0.5
  Accept-Encoding: gzip,deflate
  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
  Keep-Alive: 300
  Connection: keep-alive
  Authorization: Basic cGlwcG86dmllbm5hMDA=
  HTTP/1.x 503 Server Error
  Date: Thu, 05 May 2005 01:26:49 GMT
  Message-Id: c0829422-bd04-11d9-8726-00025576b4c0
  Server: WebSEAL/4.1.0.0 (Build 020926)
  Cache-Control: no-cache
  Pragma: no-cache
  Connection: close
  

Local fix

Problem summary

•  see main problem description
  

Problem conclusion

•  The fix for this APAR is expected to be cont
  ained in the following maintenance delivery vehicle:
  | LA interim fix | 5.1.0-TIV-AWS-LA0016
  

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