Opened 10 years ago

Closed 10 years ago

#410 closed design (fixed)

HTTPS and Shared Caching

Reported by: mnot@… Owned by: mnot@…
Priority: normal Milestone: 22
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:


p1 2.7.2 currently says that HTTPS uri responses "... MUST NOT be reused for shared caching." If true, this requirement needs to be explicitly added to p6, and referenced from here.

Change History (6)

comment:1 Changed 10 years ago by mnot@…

  • Component changed from non-specific to p1-messaging
  • Owner set to draft-ietf-httpbis-p1-messaging@…
  • Severity changed from Active WG Document to In WG Last Call

In Atlanta:

rf: the statement in question only applies to agent-side intermediaries and user agents, not to content accelerators, which are part of the origin server

rf: some user agents use a common interface to make the request, then have separate logic to decide how that information is made available to other users

rf: to know whether it is safe to send to other servers, you have to know the content

mnot: you can use Cache-Control

...some disagreement here

roberto peon: there are transformative intermediaries; we don't need to specify this

mnot: need to know who this applies to

rf: this applies to libraries in clients

mnot: segregation... a shared cache can even apply to the same box

martin t: 'never "public"' contradicts what has been said about caching rules

paul leach: override

Patrick McManus?: on a phone, different apps can share the same network context

comment:2 Changed 10 years ago by mnot@…

  • Owner changed from draft-ietf-httpbis-p1-messaging@… to mnot@…

comment:3 Changed 10 years ago by fielding@…

From [2040]:

https scheme does not imply cache must be private; addresses #410

comment:4 Changed 10 years ago by fielding@…

  • Milestone changed from unassigned to 22
  • Resolution set to incorporated
  • Status changed from new to closed

comment:5 Changed 10 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:6 Changed 10 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.