Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmLXK-00054S-Ni for pgadmin-hackers@arkaria.postgresql.org; Tue, 20 Sep 2016 13:56:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bmLXJ-0002PX-Jn for pgadmin-hackers@arkaria.postgresql.org; Tue, 20 Sep 2016 13:56:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bmLXJ-0002PO-5g for pgadmin-hackers@postgresql.org; Tue, 20 Sep 2016 13:56:37 +0000 Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bmLXD-0007hZ-HQ for pgadmin-hackers@postgresql.org; Tue, 20 Sep 2016 13:56:36 +0000 Received: by mail-wm0-x231.google.com with SMTP id l132so36628967wmf.1 for ; Tue, 20 Sep 2016 06:56:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=dn9HmrD6WHO/gdQ2FvBHQ+DZ0Awg2xBQjlGKkT5VrGo=; b=epORh7V9quq3mizm1gfIkdmtDFV0YbMJVAmHlm0SJ+KSbCp/Xs+fFZcHErwERLtTt/ U4YcIxnvieshnYMysdKBmOnJ0dKHBGPFGql6v5dsrUBmJuhSnMBNAAs6nDBzx+ih+yvG q/P31EFvzHx+ze9uxmFVYZ7GVjOthee/00bHgr1UFDa+IAqKCFUylnS6IQR52GvffL1x SdIQTkQJ4uHAZolpMOuSFGUnluJd5oj1bPPoG2aIytPGKF0/n0mmbO5q5l4zi6k+4Kq/ msyy/lGYza9ck2Ka01FnING1lkgPxQBQXfnljlaNKvYpp17GTyblhqOsE8q9jK3mzVgk aWzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=dn9HmrD6WHO/gdQ2FvBHQ+DZ0Awg2xBQjlGKkT5VrGo=; b=IW+fy7TmFgyOQBmiLoAHEOK4d93KfEaB976kbHxk8g9MsqEngIixW3/iRtdv3XmSzu RVd7lKlhNhc8GQhu4Thyr9pPCagnX3Yi2pmugG/EWkDmzcfVR9/paocSYmkVaxqK2O8C UPJPau9KrIgPbAp1OSJYMlSZeiCjZE0MZWI/tnG1ZZPynkbwKpdGdz1pcWsPFp+u/9kg /E+ruuvQmfzRkidcalmnp9x4yDLMuR6veL7mQLcM96qQAjM5V/rNfIgkJGDtsDEV3hQq 4zYPaYbd2DrmyQrBe07TWww7BcrdCXjDsLFrSycsLboOfUk73TNmiFv3vJYLjiHOt068 xYjQ== X-Gm-Message-State: AE9vXwMEC+WztIFa6XSGWhL88ZX5Zh13iVJy/KpfdWDU9Is82+KiMPld22+gypcXLXGF5M+X16fnjEBefuOpMHRj X-Received: by 10.194.89.228 with SMTP id br4mr27725831wjb.187.1474379787313; Tue, 20 Sep 2016 06:56:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.172.198 with HTTP; Tue, 20 Sep 2016 06:55:56 -0700 (PDT) In-Reply-To: References: From: Surinder Kumar Date: Tue, 20 Sep 2016 19:25:56 +0530 Message-ID: Subject: Re: [pgAdmin4][Patch]: RM1171 - Fix IE caching issue To: pgadmin-hackers Content-Type: multipart/alternative; boundary=047d7bf10ada7cb014053cf0cbe5 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --047d7bf10ada7cb014053cf0cbe5 Content-Type: text/plain; charset=UTF-8 This patch has some issue in chrome while loading nodes. I will send updated patch. On Tue, Sep 20, 2016 at 7:16 PM, Surinder Kumar < surinder.kumar@enterprisedb.com> wrote: > Hi > > *Issue:* > IE always caching the response data returned from the server and when same > request is made for next time, it doesn't bring new data, instead it use > cached data. > > *Solution:* > Set cache to '*no-cache*' in response headers while sending from the > server side. This prevents browser from caching data every time an http > request is made. > > Thanks to Harshal & Murtaza for discussing issue and solution. > > Please find attached patch and review. > > > Thanks, > Surinder Kumar > --047d7bf10ada7cb014053cf0cbe5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thi= s patch has some issue in chrome while loading nodes. I will send updated p= atch.

= On Tue, Sep 20, 2016 at 7:16 PM, Surinder Kumar <surinder.ku= mar@enterprisedb.com> wrote:
H= i

Issue:
IE always caching= the response data returned from the server and when same request is made f= or next time, it doesn't bring new data, instead it use cached data.

Solution:
Set cache to '= no-cache' in response headers while sending from the server side= . This prevents browser from caching data every time an http request is mad= e.

Thanks to Harshal &= ; Murtaza for discussing issue and solution.

Please find attached patch and review.


Thanks,
Surinder Kumar

--047d7bf10ada7cb014053cf0cbe5--