Return-Path: X-Original-To: apmail-jmeter-user-archive@www.apache.org Delivered-To: apmail-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A1BDDD37 for ; Fri, 10 Aug 2012 23:03:31 +0000 (UTC) Received: (qmail 67430 invoked by uid 500); 10 Aug 2012 23:03:30 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 67397 invoked by uid 500); 10 Aug 2012 23:03:30 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 67387 invoked by uid 99); 10 Aug 2012 23:03:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2012 23:03:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shettyd@gmail.com designates 209.85.214.171 as permitted sender) Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com) (209.85.214.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Aug 2012 23:03:24 +0000 Received: by obqv19 with SMTP id v19so3007066obq.2 for ; Fri, 10 Aug 2012 16:03:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GHnj1oSvMtiKLxMMXr/TQ9xG2Ku6rjUSZwb10PMYb3U=; b=tL0wWHUGa9eW8fUmYbEj31XG1iMN5OAqmlOQzNvvZegWEONY3MNTGp2l1D1g3bUtSi PjvaVFjwVb/5GMBQ9cKMnoq4NOPb/isIq6tdPS6xrpTn4HtoTWXUP0DyD5FrU3pVTb2q BkHkbu+eQl3f5bRCHdrQfbn2iBhwALH91vxvbgwvpVHuY02cMI4zInaCvZPxh4tFZM5J fVDiedBANvY0jrg3PXPSawWEoiFwngv42s9tqWzXThAX8XWvaktEuAucS/0Vc+1Am59m 6CdvPladD6XtkIhG4sxD7TR2WKQO/Cga+IP1Ob9OaODx8uLSWJ+1UBlJ99q8R0UctKLT gOAQ== MIME-Version: 1.0 Received: by 10.182.152.97 with SMTP id ux1mr1666793obb.13.1344639783667; Fri, 10 Aug 2012 16:03:03 -0700 (PDT) Received: by 10.182.35.135 with HTTP; Fri, 10 Aug 2012 16:03:03 -0700 (PDT) In-Reply-To: References: Date: Fri, 10 Aug 2012 16:03:03 -0700 Message-ID: Subject: Re: HTTP POST to a redirected URL handled properly? From: Deepak Shetty To: JMeter Users List Content-Type: multipart/alternative; boundary=f46d04462c0aa8089b04c6f15802 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04462c0aa8089b04c6f15802 Content-Type: text/plain; charset=ISO-8859-1 > If not, is this the correct user agent and test tool behavior to expect when coming across a 302 redirect for POST requests? Yes a redirect is always a GET regards deepak On Fri, Aug 10, 2012 at 3:56 PM, David Luu wrote: > Hi, > > This is first time I've come across this topic. By the way, I'm testing > APIs that are under development so things might change, will follow up on > them later but assuming correct server setup: > > I make POST to a URL and it returned 302 moved temporarily with new URL. > The redirect is basically changing original URL of HTTP to HTTPS, that's > it. In JMeter, I'm using an HTTP sampler and by default have the follow > redirect option checked. It did follow the redirect but POST request became > a GET and thus all POST data was lost and API call failed. I didn't specify > a specific HTTP client to use, using system default. If it matters, which > HTTP client is best suited for this? I was wondering whether under this > situation JMeter can follow redirect but keep as POST request with same > posted data? If so, how? If not, is this the correct user agent and test > tool behavior to expect when coming across a 302 redirect for POST > requests? > > Regards, > David > --f46d04462c0aa8089b04c6f15802--