On Mon, Oct 03, 2011 at 05:13:35PM +0100, Ben Summers wrote:
> Might be best to also add in 'private'
>
> Cache-Control: private, no-cache
>
> for a more explicit description of the intent of only showing content to the
> user who requested it.
That's wrong. It should have a Vary header to re
On 3 Oct 2011, at 17:37, Lluís Batlle i Rossell wrote:
> On Mon, Oct 03, 2011 at 05:13:35PM +0100, Ben Summers wrote:
>>
>> On 3 Oct 2011, at 16:20, Lluís Batlle i Rossell wrote:
>>> I think that's exactly what I want. Anyone against?
>>
>> Might be best to also add in 'private'
>>
>> Cache-C
On Mon, Oct 03, 2011 at 06:47:12PM +0200, Stephan Beal wrote:
> 2011/10/3 Lluís Batlle i Rossell
>
> > If ever appears the need, let's introduce "private".
> >
> > I committed the removal of no-store, btw.
> >
> >
> Wouldn't it be just as easy to set the whole string as a config option,
> default
2011/10/3 Lluís Batlle i Rossell
> If ever appears the need, let's introduce "private".
>
> I committed the removal of no-store, btw.
>
>
Wouldn't it be just as easy to set the whole string as a config option,
defaulting to something sane?
--
- stephan beal
http://wanderinghorse.net/home/st
On Mon, Oct 03, 2011 at 05:13:35PM +0100, Ben Summers wrote:
>
> On 3 Oct 2011, at 16:20, Lluís Batlle i Rossell wrote:
> > I think that's exactly what I want. Anyone against?
>
> Might be best to also add in 'private'
>
> Cache-Control: private, no-cache
>
> for a more explicit description o
On 3 Oct 2011, at 16:20, Lluís Batlle i Rossell wrote:
> On Mon, Oct 03, 2011 at 05:05:13PM +0200, Stephan Beal wrote:
>> 2011/10/3 Lluís Batlle i Rossell
>>
>>> What would happen if JSON answers had not 'no-store'? Would not be
>>> 'no-cache'
>>> enough? It should be up to the json clients tho
On Oct 3, 2011, at 17:20 , Lluís Batlle i Rossell wrote:
> I think that's exactly what I want. Anyone against?
I'm for it, but here's the ticket referring to "no-store" that mentions some
problems with Opera:
http://www.fossil-scm.org/index.html/info/b465b3bc2ceef4446b2ae770242ed0968e4dbc68
--
2011/10/3 Lluís Batlle i Rossell
> I think that's exactly what I want. Anyone against?
>
Sounds perfect to me :).
--
- stephan beal
http://wanderinghorse.net/home/stephan/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lis
On Mon, Oct 03, 2011 at 05:05:13PM +0200, Stephan Beal wrote:
> 2011/10/3 Lluís Batlle i Rossell
>
> > What would happen if JSON answers had not 'no-store'? Would not be
> > 'no-cache'
> > enough? It should be up to the json clients though.
> >
>
> Sorry, my mistake - i meant no-cache, not no-st
2011/10/3 Lluís Batlle i Rossell
> What would happen if JSON answers had not 'no-store'? Would not be
> 'no-cache'
> enough? It should be up to the json clients though.
>
Sorry, my mistake - i meant no-cache, not no-store.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
_
On Mon, Oct 03, 2011 at 04:34:19PM +0200, Stephan Beal wrote:
> 2011/10/3 Lluís Batlle i Rossell
>
> > Small research about the trouble: Cache-Control: no-store
> >
> >
> > http://blogs.atlassian.com/developer/2007/12/cachecontrol_nostore_considere.html
> > https://jira.atlassian.com/browse/JRA-
2011/10/3 Lluís Batlle i Rossell
> Small research about the trouble: Cache-Control: no-store
>
>
> http://blogs.atlassian.com/developer/2007/12/cachecontrol_nostore_considere.html
> https://jira.atlassian.com/browse/JRA-14031
>
> I'd prefer not to switch to chrome. :) What about removing no-stor
On Mon, Oct 03, 2011 at 03:43:39PM +0200, Dmitry Chestnykh wrote:
> > sometimes I'm filling a ticket, and I click to some link by error, and then
> > I
> > use back/forward to go to the ticket form page again. And the form is blank.
> >
> > Firefox uses to store the form contents along page back/
> sometimes I'm filling a ticket, and I click to some link by error, and then I
> use back/forward to go to the ticket form page again. And the form is blank.
>
> Firefox uses to store the form contents along page back/forward, but it fails
> to
> do so for fossil. Can this be 'fixed'? Anyone awa
Hello,
sometimes I'm filling a ticket, and I click to some link by error, and then I
use back/forward to go to the ticket form page again. And the form is blank.
Firefox uses to store the form contents along page back/forward, but it fails to
do so for fossil. Can this be 'fixed'? Anyone aware of
15 matches
Mail list logo