On Tue, Feb 12, 2013 at 1:36 PM, Anne van Kesteren wrote:
> On Tue, Feb 12, 2013 at 7:30 PM, Monsur Hossain wrote:
> > On Tue, Feb 12, 2013 at 3:37 AM, Anne van Kesteren
> wrote:
> >> User credentials stored by the user agent based on a previous visit to
> the
> &
On Tue, Feb 12, 2013 at 3:37 AM, Anne van Kesteren wrote:
> On Tue, Feb 12, 2013 at 4:24 AM, Monsur Hossain wrote:
> > The XHR spec defines "user credentials" as "cookies, HTTP authentication,
> > and client-side SSL certificates". Its not clear to me what &qu
ain, or polling a particular endpoint).
So I'm concerned that the cache-hit ratio in real world applications will
actually be quite low. It would be nice to have some sort of solution to
this.
Thanks,
Monsur
On Wed, Apr 18, 2012 at 11:50 AM, Anne van Kesteren wrote:
> On Wed, 18 Apr 2012
- Cache lookup applies to *any* origin making requests to the
domain.
This would fit in with the current preflight caching model while still
allowing some flexibility to servers implementing CORS.
Thanks,
Monsur
On Wed, Apr 18, 2012 at 7:16 AM, Anne van Kesteren wrote:
> On Tue, 17 Apr 20
Hi there. The CORS spec currently indicates that the preflight cache should
store preflight responses for a particular origin/request url pair. That
means that multiple requests to different urls on the same domain will
always trigger a preflight, even if the preflight response is exactly the
same
