Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7DCBC18832 for ; Fri, 26 Feb 2016 00:31:58 +0000 (UTC) Received: (qmail 97116 invoked by uid 500); 26 Feb 2016 00:31:58 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 97067 invoked by uid 500); 26 Feb 2016 00:31:58 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 97053 invoked by uid 99); 26 Feb 2016 00:31:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Feb 2016 00:31:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 698081A086B for ; Fri, 26 Feb 2016 00:31:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.198 X-Spam-Level: * X-Spam-Status: No, score=1.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id FhnS1dWw9IKv for ; Fri, 26 Feb 2016 00:31:56 +0000 (UTC) Received: from mail-qg0-f45.google.com (mail-qg0-f45.google.com [209.85.192.45]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 554505F640 for ; Fri, 26 Feb 2016 00:31:56 +0000 (UTC) Received: by mail-qg0-f45.google.com with SMTP id b67so54174882qgb.1 for ; Thu, 25 Feb 2016 16:31:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=4uZVoSCAWfDType+ncS233XT8Nz/KrT0BVG+BfPahYo=; b=PQgp7/DvUMxuMVeKxMPd/FJmiyBHamgxJlWMa+mSPJ7Apk1UwGy0UR8IYqW/PxfQnU ZivlLUwWseZYIaWm06pEzjnvde2/LxGop+KmT7r/BfqDWiXiOh4AkY/m6WCOB7JQ5Yi7 zrl5bft+LEeAiAykJnKC2tpKszMWvbbLJ3Nz+QPtcrMh6I1XzsOWwOETaR66H1mwmiZ8 g43ciVp7P6k2eMMQB5f1GAEfWpuysRFQLtaFG+VGbsG8sPiqv2PjeCG8627PpVokM5ya g0YbCMFnwlxFkIIGlI+FG6Lx62v5cpbQeM+11+hiIkLgP1syM8hq+hyMVPmzw6ltiWfr 6jKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :content-type; bh=4uZVoSCAWfDType+ncS233XT8Nz/KrT0BVG+BfPahYo=; b=EPqWQsyePThlRnmNMd1fjFEEoJeF8lXXisNW5MYNH1FXIEQBYlluY4NnoelMyyEMIY grV+RY6qEH55uFLMfZa1qHmwBB2Om730TZxfTBBMzJ8wDJrC608LY4w6srCvxtDXnYhZ EbbXuQPvDVXRNoWcOIhzMm92rZISbxSuPLjodOunfWKXg80GokcnGjt8iLGQdDhK+C3J RSD5ZDTFoZYxMAbelBW8s9OKhYUwdXa/JczruOzGn3ZDwGXTpI7Sw5Q68fDeEB274Lj5 FDJCQfDvYqwoZ/91n8Prk7nzeFnryuNzw6G8Z+w2juxeW36g0OjzsMMIRVJJhiZ++ymU /6cg== X-Gm-Message-State: AG10YORA3rYiytVN0Ayzs2iM3axwDH5wQcRugByyjGuEd32gJDmWZsNnJsNaQk1nzPbEWNvPLlBmvXb/nZt6Tw== MIME-Version: 1.0 X-Received: by 10.140.82.146 with SMTP id h18mr61044345qgd.26.1456446710589; Thu, 25 Feb 2016 16:31:50 -0800 (PST) Received: by 10.55.116.65 with HTTP; Thu, 25 Feb 2016 16:31:50 -0800 (PST) Date: Fri, 26 Feb 2016 01:31:50 +0100 Message-ID: Subject: CookieSpecs : Which one to choose ? From: Philippe Mouawad To: HttpClient User Discussion Cc: "dev@jmeter.apache.org" Content-Type: multipart/alternative; boundary=001a11c12c74d1ac9d052ca16c5d --001a11c12c74d1ac9d052ca16c5d Content-Type: text/plain; charset=UTF-8 Hello, I am not sure what should be the default Cookie Policy for JMeter 3.0 with HC4.5.2 As per HttpClient doc: https://github.com/apache/httpclient/blob/4.5.x/httpclient/src/main/java/org/apache/http/client/config/CookieSpecs.java Standard seems the best: - The RFC 6265 compliant policy (interoprability profile). But default : - The default policy. This policy provides a higher degree of compatibility with common cookie management of popular HTTP agents for non-standard (Netscape style) cookies. Do browsers accept the 2 , in this case should we create a CookieSpec implementation that delegate to DefaultCookieSpec and RFC6265LaxSpec ? -- Cordialement. Philippe Mouawad. --001a11c12c74d1ac9d052ca16c5d--