native SP logger enhancement: include applicationId

[Cantor, Scott]

> Well, I'm not in the shibboleth business for enough time to find anything self-
> evident here :)

Not a Shibboleth issue. SSO systems either preserve POST or they don't. If they don't, SSO interrupts break a POST. Shibboleth happens to allow limited POST preservation in certain cases if it's enabled, and it's not enabled, so it logs an INFO message, and while that probably should just be DEBUG I'm likely to leave it alone and just move the default level to WARN.

> More seriously, it doesn't explain why they are so many of those messages,
> if the cause is on my side, and if I can do something to make the world better
> someway: 4000 interrupted POST requests/hour means 6% of the total
> number of HTTP requests serviced by this proxy during the same time
> period. Hence the need to pinpoint the issue more precisely.

Timeouts are the usual reason for SSO in the middle of a POST, but misconfigured systems that cause sessions to invalidate would be another. Given your earlier note, it would seem that perhaps address mismatches might be a cause.

-- Scott