A strange case for catching an exception

Hi Aaron,

 

 

I'm running this in HTTP_REQUEST... I will be using lthompson's suggestion of including the authorization header and the HTTP method in the logged information, it's a fantastic idea and should help pinpoint where the runtime error is coming from. I will post what I find out as soon as I get the info. Unfortunately, despite the enormous number of connections, I've only seen about a dozen occurrences of the error over the past few days, so whatever client it is - they're not trying too terribly hard ;)

 

 

Thanks for the catch too on the unneeded user agent variable. I'll take that out, it's unnecessary.

 

 

Thanks,

 

Jen