idp3 "Message was expired" and http status code 500

[Jarno Huuskonen]

Hi,

Is it "normal" for idp3 (3.1.2) to reply with http error/status code 500
(internal server error) when client sends expired saml message.
(I'm using tomcat if that makes a difference).

Idp logs this expired message:
"Message was expired: message issue time was '2015-08-30T01:02:40.000Z',
message expired at: '2015-08-30T01:08:40.000Z', current time:
'2015-09-04T08:34:07.121+03:00'"

and http access_log:
ip.add.re.ss - - [04/Sep/2015:08:38:16 +0300] "GET /idp/profile/SAML2/Redirect/SSO?SAMLRequest=fZFRT4MwFI_REST_OF_SAML_REMOVED HTTP/1.1" 500 1332

Is it possible to modify the http status code thats sent for "message
was expired" requests ? Using 500(internal server error) makes it
hard/impossible to use load balancer feature that tracks backend responses and
marks server down if it starts replying with too many 50x errors.

For example sending "GET /idp/profile/SAML2/Redirect/SSO" (no
SAMLRequest) gets 400(Bad Request) ...

-Jarno

-- 
Jarno Huuskonen