seemingly inconsistent responses to SP requests

[Cantor, Scott]

On 12/28/16, 5:33 PM, "users on behalf of IAM David Bantz" <users-bounces at shibboleth.net on behalf of dabantz at alaska.edu> wrote:

> That is, the ERROR couldn't be in response to that request (merely "nearby" in the logs) but some other malformed or
> bogus request.

Correct, that's what I meant by misassociating, you're incorrectly correlating two log events. At minimum make sure you have the IP address added into the log messages, I don't know that much else will work reliably though you could log the container session too if you really wanted to. But even if it's the same client, those aren't the same request.

>    Yes, that makes sense; thank you; in fact with that hint I think I've deduced the source as a periodic Status request issued
> from a monitoring service.
    
That's another common case, but a production log will be riddled with back button issues, that's just unavoidable. You get used to it and/or eventually filter them out once they're just noise. At least the users now get a consistent message on those, I shipped it with the behavior I've always used with V2.

-- Scott