Google Mail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Message from discussion 400 bad request

View Parsed - Show only message text

Received: by 10.103.214.13 with SMTP id r13mr207037muq.5.1233770445491;
        Wed, 04 Feb 2009 10:00:45 -0800 (PST)
Return-Path: <ja...@amee.cc>
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.184])
        by mx.google.com with ESMTP id 5si1822470fge.12.2009.02.04.10.00.45;
        Wed, 04 Feb 2009 10:00:45 -0800 (PST)
Received-SPF: neutral (google.com: 209.85.128.184 is neither permitted nor denied by best guess record for domain of ja...@amee.cc) client-ip=209.85.128.184;
Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.128.184 is neither permitted nor denied by best guess record for domain of ja...@amee.cc) smtp.mail=ja...@amee.cc
Received: by fk-out-0910.google.com with SMTP id 19so2189536fkr.10
        for <amee-developer@googlegroups.com>; Wed, 04 Feb 2009 10:00:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.241.8 with SMTP id o8mr389166bkh.102.1233770445243; Wed, 
	04 Feb 2009 10:00:45 -0800 (PST)
In-Reply-To: <f6dfb48d-364d-4b4c-a2b5-31a7765e54d4@g39g2000pri.googlegroups.com>
References: <f6dfb48d-364d-4b4c-a2b5-31a7765e54d4@g39g2000pri.googlegroups.com>
Date: Wed, 4 Feb 2009 18:00:45 +0000
Message-ID: <d0edc4c60902041000l6ac0d89el4cd0c8545e9b566a@mail.gmail.com>
Subject: Re: [amee-developer] 400 bad request
From: James Smith <ja...@amee.cc>
To: amee-developer@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

2009/2/4 cipher_neo <l33...@gmail.com>:
> I am currently using the API for www.edenbee.com
> We are having intermittent issues where we receive a 400 bad_request
> error message back from the api on post requests. It only happens
> sometimes and i am using the same post data for each request. Just
> wondering can you guys maybe shed some light on this issue for me.

Can you send us details of the POST you are sending, or even better a
log of the actual HTTP transaction itself? If you can give us more
details, we can try to identify the problem for you.

cheers,
James Smith

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google