Re: Last-Modified HTTP header in GET responses

2019-09-04 Thread Johan Corveleyn
On Wed, Sep 4, 2019 at 2:47 PM Johan Corveleyn wrote: > > On Wed, Sep 4, 2019 at 2:01 PM Branko Čibej wrote: > > > > On 04.09.2019 11:44, Johan Corveleyn wrote: > > > On Tue, Sep 3, 2019 at 8:01 AM Branko Čibej wrote: > > [...] > > >>> Anyway, how about bringing this feature back in some form? >

Re: Last-Modified HTTP header in GET responses

2019-09-04 Thread Johan Corveleyn
On Wed, Sep 4, 2019 at 2:01 PM Branko Čibej wrote: > > On 04.09.2019 11:44, Johan Corveleyn wrote: > > On Tue, Sep 3, 2019 at 8:01 AM Branko Čibej wrote: > [...] > >>> Anyway, how about bringing this feature back in some form? > >>> - Revert r1724790? > >> This is clearly the simplest solution, b

Re: Last-Modified HTTP header in GET responses

2019-09-04 Thread Branko Čibej
On 04.09.2019 11:44, Johan Corveleyn wrote: > On Tue, Sep 3, 2019 at 8:01 AM Branko Čibej wrote: [...] >>> Anyway, how about bringing this feature back in some form? >>> - Revert r1724790? >> This is clearly the simplest solution, but I have no idea what the >> performance impact would be. From lo

Re: Last-Modified HTTP header in GET responses

2019-09-04 Thread Johan Corveleyn
On Tue, Sep 3, 2019 at 8:01 AM Branko Čibej wrote: > > On 02.09.2019 16:20, Johan Corveleyn wrote: > > On Fri, Jan 15, 2016 at 1:58 PM Ivan Zhakov wrote: > >> On 7 January 2016 at 10:34, Ivan Zhakov wrote: > >>> On 6 January 2016 at 08:14, Greg Stein wrote: > Personally, I'd be more intere