From jmeter-user-return-17164-apmail-jakarta-jmeter-user-archive=jakarta.apache.org@jakarta.apache.org Thu Aug 02 14:46:34 2007 Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 36060 invoked from network); 2 Aug 2007 14:46:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Aug 2007 14:46:33 -0000 Received: (qmail 2937 invoked by uid 500); 2 Aug 2007 14:46:31 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 2917 invoked by uid 500); 2 Aug 2007 14:46:31 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 2906 invoked by uid 99); 2 Aug 2007 14:46:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2007 07:46:31 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [62.204.33.81] (HELO siteint-1000.datagate.net.uk) (62.204.33.81) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2007 14:46:05 +0000 Received: from sideshow.site-intelligence.co.uk ([91.143.176.244]) by siteint-1000.datagate.net.uk (8.12.11.20060308/8.12.8) with ESMTP id l72DXYi1019420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 2 Aug 2007 14:33:35 +0100 Received: from dangermouse.site-intelligence.local (dangermouse.site-intelligence.local [192.168.2.134]) by sideshow.site-intelligence.co.uk (Postfix) with ESMTP id 8BE8BE38E2 for ; Thu, 2 Aug 2007 15:40:46 +0100 (BST) From: Andrzej Doyle To: "JMeter Users List" Subject: Re: Simple port problem about Jmeter. Date: Thu, 2 Aug 2007 15:46:00 +0100 User-Agent: KMail/1.9.5 References: <823A93EED437D048963A3697DB0E35DE19199D@pdsmsx414.ccr.corp.intel.com> In-Reply-To: <823A93EED437D048963A3697DB0E35DE19199D@pdsmsx414.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708021546.01094.andrzej@andrzejdoyle.co.uk> X-Virus-Checked: Checked by ClamAV on apache.org On Thursday 02 August 2007 10:25, Jiang, Yangyang wrote: > Hi, all! > >I just want to ask > how Jmeter proxy server will link to the none-80 destination when you > must record your actions instead of writing them. It will do this the same way it handles all requests - there shouldn't be a problem with running on strange ports, or the fact that your application and the proxy are on the same host. The browser knows where you want to link to based on what you type in the address bar, like it always does. But when you have a proxy server set (in this case the JMeter one), instead of going ahead and making the request to the specified URL, it goes and tells the proxy server "I want to make a request like this". The JMeter proxy will record this request and then go ahead and make it any, returning the response. So essentially you can consider the proxy as a transparent sniffer, sitting on the wire between your browser and the server(s), recording the requests that go by. Because of this it will always capture the host, port, path, query string, POSTDATA, etc. irrespective of where the server is hosted. So, the short answer to your question is "it just works". :-) Andrzej --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org