Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f12X1-0006xl-Lb for pgadmin-hackers@arkaria.postgresql.org; Wed, 28 Mar 2018 04:17:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f12X0-0003XO-3D for pgadmin-hackers@arkaria.postgresql.org; Wed, 28 Mar 2018 04:17:50 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f12Wz-0003XD-Le for pgadmin-hackers@lists.postgresql.org; Wed, 28 Mar 2018 04:17:49 +0000 Received: from smtp.twyn.com ([194.112.241.8]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f12Ww-0001nv-7d for pgadmin-hackers@lists.postgresql.org; Wed, 28 Mar 2018 04:17:48 +0000 Received: from localhost (unknown [127.0.0.1]) by smtp.twyn.com (Postfix) with ESMTP id 35578120DF6; Wed, 28 Mar 2018 04:17:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=twyn.com; h= x-mailer:content-type:content-type:mime-version:subject:subject :references:in-reply-to:message-id:from:from:date:date:received :received:received:received:received; s=mail; t=1522210661; x= 1524025062; bh=tyfiMd4N9NFOT5pm8h7CJfuBQYyOJOcd0P6Tmc+LTgQ=; b=g zcPYGWMuGuO3yxRaOcf+K1mfYJkf2iSGvOhU9tEVENXHu05x8oxgi9uPFuoGqBf6 phcjxsp5VVbLK37s+YxC8FXvgTPgB4uJ/oVZm7hSS/QH8R9PpSnjQ5LkPhsCdGsQ LMQrPqsw8TChA12/KVquDUhYKuFK1FgPSoAaJ++Fgs= X-Virus-Scanned: amavisd-new at twyn.com Received: from smtp.twyn.com ([127.0.0.1]) by localhost (smtp.twyn.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nroY1R5EWSxj; Wed, 28 Mar 2018 06:17:41 +0200 (CEST) Received: from at460ex01.connexgroup.net (at460ex01.connexgroup.net [192.168.2.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.twyn.com (Postfix) with ESMTPS id 62149120CBD; Wed, 28 Mar 2018 06:17:41 +0200 (CEST) Received: from at460ex01.connexgroup.net (localhost [127.0.0.1]) by at460ex01.connexgroup.net (Postfix) with ESMTPS id 190A416E5EB4; Wed, 28 Mar 2018 06:17:41 +0200 (CEST) Received: from at460ex01.connexgroup.net (localhost [127.0.0.1]) by at460ex01.connexgroup.net (Postfix) with ESMTPS id E8DA416E6109; Wed, 28 Mar 2018 06:17:40 +0200 (CEST) Received: from at460ex01.connexgroup.net (AT460EX01.connexgroup.net [192.168.2.35]) by at460ex01.connexgroup.net (Postfix) with ESMTP id CE1E116E5EB4; Wed, 28 Mar 2018 06:17:40 +0200 (CEST) Date: Wed, 28 Mar 2018 06:17:40 +0200 (CEST) From: Wilhelm Wurzer To: Murtuza Zabuawala Cc: pgadmin-hackers Message-ID: <503352418.2730384.1522210660636.JavaMail.zimbra@connexgroup.net> In-Reply-To: References: <96167950.2563944.1522151063432.JavaMail.zimbra@connexgroup.net> <624110606.2586732.1522153466523.JavaMail.zimbra@connexgroup.net> <954747366.2588213.1522154105646.JavaMail.zimbra@connexgroup.net> Subject: Re: pgadmin healthcheck-url MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2730383_1914417137.1522210660633" X-Originating-IP: [192.168.2.205] X-Mailer: Zimbra 8.6.0_GA_1162 (ZimbraWebClient - GC65 (Linux)/8.6.0_GA_1162) Thread-Topic: pgadmin healthcheck-url Thread-Index: Y+YSqWJstgUG8la2s4v0EjFcLnNvlw== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_2730383_1914417137.1522210660633 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,=20 i did the test in the browser (chrome), but it can as well be reproduced us= ing "curl". The logging ('-v') shows that the session cookies is sent with = the response.=20 [ec2-user@ip-10-0-7-174 ~]$ curl -v http://10.0.7.174:8084/misc/ping=20 * Trying 10.0.7.174...=20 * TCP_NODELAY set=20 * Connected to 10.0.7.174 (10.0.7.174) port 8084 (#0)=20 > GET /misc/ping HTTP/1.1=20 > Host: 10.0.7.174:8084=20 > User-Agent: curl/7.53.1=20 > Accept: */*=20 >=20 < HTTP/1.1 200 OK=20 < Date: Wed, 28 Mar 2018 04:13:14 GMT=20 < Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips mod_wsgi/3.4 Python/2.7= .5=20 < Set-Cookie: pga4_session=3D"3fe44565-2f57-49f0-8674-df6f710fae07!kHKTBGuk= +SBKUy+TN2r6XlAyKAI=3D"; Expires=3DThu, 29-Mar-2018 04:13:14 GMT; HttpOnly;= Path=3D/=20 < Content-Length: 4=20 < Content-Type: text/html; charset=3Dutf-8=20 <=20 * Connection #0 to host 10.0.7.174 left intact=20 PING=20 Wilhelm Wurzer=20 Von: "Murtuza Zabuawala" =20 An: "Wilhelm Wurzer" =20 CC: "pgadmin-hackers" =20 Gesendet: Dienstag, 27. M=C3=A4rz 2018 16:40:35=20 Betreff: Re: pgadmin healthcheck-url=20 I'm not able to re-produce the behaviour when using browser.=20 - Could you let us know the exact steps to re-produce the issue?=20 - How did you trigger http request to hit '/ping' url?=20 --=20 Regards,=20 Murtuza Zabuawala=20 EnterpriseDB: http://www.enterprisedb.com=20 The Enterprise PostgreSQL Company=20 On Tue, Mar 27, 2018 at 6:05 PM, Wilhelm Wurzer < wilhelm.wurzer@twyn.com >= wrote:=20