On Thu, Jun 19, 2014 at 3:26 PM, J. Landman Gay
wrote:
>
> 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
On 6/17/2014, 3:56 PM, Trevor DeVore wrote:
On Tue, Jun 17, 2014 at 1:06 PM, J. Landman Gay
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
On Tue, Jun 17, 2014 at 1:06 PM, J. Landman Gay
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 a
On 6/17/2014, 12:25 AM, Mark Wieder wrote:
Jacque-
Monday, June 16, 2014, 8:56:40 PM, you wrote:
Maybe a better question to everyone would be: can a server 400 error be
related to a bad SSL certificate chain?
I'd expect something more like a 401 for a security problem. The
official definitio
On 6/16/2014, 11:08 PM, Trevor DeVore wrote:
On Mon, Jun 16, 2014 at 3:25 PM, J. Landman Gay
wrote:
I need help figuring out why AWS is returning an error 400 "bad request"
in a limited number of cases. We have a test group of some dozens of people
and only 2 have the problem.
I think that
Jacque-
Monday, June 16, 2014, 8:56:40 PM, you wrote:
> Maybe a better question to everyone would be: can a server 400 error be
> related to a bad SSL certificate chain?
I'd expect something more like a 401 for a security problem. The
official definition of a 400 response is "malformed syntax".
On Mon, Jun 16, 2014 at 3:25 PM, J. Landman Gay
wrote:
> I need help figuring out why AWS is returning an error 400 "bad request"
> in a limited number of cases. We have a test group of some dozens of people
> and only 2 have the problem.
>
I think that some XML should be sent back by the server
On 6/16/2014, 10:28 PM, J. Landman Gay wrote:
I'm just doing a GET to a URL. There is an SQS queue (I'm not sure what
that is actually,) which is being processed server-side. I think we need
to know what's happening before my request hits the queue.
I should expand that a little bit. The server
On 6/16/2014, 6:21 PM, As_Simon wrote:
Sorry that was a cop-out.
I'm using CloudBerry Explorer for Amazon.
Right click on the bucket
Logging > Logging Settings or Cloudfront logging settings.
I'm in the dark about what's going on over at the server side, but on my
end, I'm just doing a GET to
Sorry that was a cop-out.
I'm using CloudBerry Explorer for Amazon.
Right click on the bucket
Logging > Logging Settings or Cloudfront logging settings.
Simon
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Diagnosing-server-error-400-tp4680498p4680
Hi Jacque,
AWS does have logs, you have to set them up for each bucket.
Simon
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Diagnosing-server-error-400-tp4680498p4680503.html
Sent from the Revolution - User mailing list archive at Nabble.com
Are you using sessions?
On Mon, Jun 16, 2014 at 2:25 PM, J. Landman Gay
wrote:
> I need help figuring out why AWS is returning an error 400 "bad request"
> in a limited number of cases. We have a test group of some dozens of people
> and only 2 have the problem.
>
> What I know:
>
> The data se
I need help figuring out why AWS is returning an error 400 "bad request"
in a limited number of cases. We have a test group of some dozens of
people and only 2 have the problem.
What I know:
The data sent to the server is the same for everyone, and is correctly
formatted. I have logs of that
13 matches
Mail list logo
