Diagnosing server error 400

[J. Landman Gay]

On 6/17/2014, 3:56 PM, Trevor DeVore wrote:
> On Tue, Jun 17, 2014 at 1:06 PM, J. Landman Gay <jacque at hyperactivesw.com>
> wrote:
>
>> On 6/16/2014, 11:08 PM, Trevor DeVore wrote:
>>>
>>> I think that some XML should be sent back by the server as well. It will
>>> contain additional error information about what went wrong. Have you
>>> looked
>>> at that?
>>>
>>
>> I have looked at it during debugging but since I don't ever get a 400
>> error I haven't seen that particular data. I'll add it to the logging
>> though so that the testers have a record, maybe that will show something.
>> Thanks.
>
>
> I think that will prove very helpful. The errors in the XML are usually
> helpful. It should tell you if the issue is with the signature, key, etc.
>

I have to thank you for this, Trevor. You were absolutely right. The XML 
told me that the request was rejected because it had expired. We're 
using signed URLs set for 15 minutes duration, but this user must have 
the wrong time zone set on their computer clock because the request was 
"expiring" hours and hours before they sent it.

Thanks so much.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com