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 89A6FC6FB for ; Sat, 11 Aug 2012 12:09:41 +0000 (UTC) Received: (qmail 76817 invoked by uid 500); 11 Aug 2012 12:09:40 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 76580 invoked by uid 500); 11 Aug 2012 12:09:37 -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 76549 invoked by uid 99); 11 Aug 2012 12:09:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Aug 2012 12:09:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andrejvanderzee@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qc0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Aug 2012 12:09:29 +0000 Received: by qcad1 with SMTP id d1so1502646qca.2 for ; Sat, 11 Aug 2012 05:09:08 -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=m+ES6nIRbezM07gONd5ffvDeM9BsJkilEQWvrkFc770=; b=MITP9Me8ht5tgCBSV3TU0Fi4MIz8im1g0uHLsMOkXS9xcoxSkxQXfca0i99Y3OiaVW Ofa4EZZnwSFchTTrEshK7DJMqttv7vykyXPTNXGLCr3YZRKWqAXiuixCXdZhXjZixb86 wUn3hfz1AQleQzspig5cuX0Bne0jqicL19/xARwl/NdLyysJdxZo6mWKJ0D2uisa2E+p VUjB8RGY7vrjFgSfJOgvGPobEHsV7obZqsISgVgV7h7piS+xWuB83r+evE580akytKVJ M0L5ak1DYGWFl1CWnkVt4Wd5QZu7uiKpm5T0Jrdg/KXd89ItV2JvcLB3sE11A3sn+Cf1 PNzw== MIME-Version: 1.0 Received: by 10.224.58.142 with SMTP id g14mr12725475qah.96.1344686948669; Sat, 11 Aug 2012 05:09:08 -0700 (PDT) Received: by 10.49.95.6 with HTTP; Sat, 11 Aug 2012 05:09:08 -0700 (PDT) In-Reply-To: References: Date: Sat, 11 Aug 2012 14:09:08 +0200 Message-ID: Subject: Re: HTTP request sampler option "Content encoding" From: Andrej van der Zee To: JMeter Users List Content-Type: text/plain; charset=ISO-8859-1 > As far as I can tell, none of the 3 HTTP implementations used by > JMeter actually support request compression. > And JMeter does not implement compression either. Then I will have to implement it myself somehow, no big deal. I was just confused because there is a "Content Type" option in the HTTP sampler which lets you specify a string, but I understood that this is to specify the character set, which I think is a bit misleading. The JMeter documentation does provide enough information to figure out what it is. >> The key difference >> is that for HTTP requests one must know beforehand if the server >> supports decompression. > > How is that determined? Often it is simply known in advance. For example if you develop an iPhone app that communicates in XML over HTTP with its server. Cheers, Andrej --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org For additional commands, e-mail: user-help@jmeter.apache.org