Re: [whatwg] unexpected use of the CORS specification

On Mon, Nov 9, 2009 at 12:35 PM, Maciej Stachowiak wrote: > > On Nov 8, 2009, at 7:25 AM, Adam Barth wrote: > >> I don't see the connection with CORS.  The browser is free to request >> whatever URLs it wants.  The results need not be accessible to >> content.  Maybe I'm misunderstanding. > > The

Re: [whatwg] unexpected use of the CORS specification

Silvia Pfeiffer wrote: ... Further, Benno suggests extending http://www.w3.org/TR/XMLHttpRequest/ with a property to disable following redirects automatically so as to be able to expose the redirection. I am not aware if somebody else has suggested these use cases for CORS and XMLHttpRequest bef

Re: [whatwg] unexpected use of the CORS specification

On Nov 8, 2009, at 7:25 AM, Adam Barth wrote: I don't see the connection with CORS. The browser is free to request whatever URLs it wants. The results need not be accessible to content. Maybe I'm misunderstanding. The proposal at the link was for a method to do URL unshortening as a clie

Re: [whatwg] unexpected use of the CORS specification

On Sun, Nov 8, 2009 at 2:08 PM, Silvia Pfeiffer wrote: > Yes, that's the point. Please read the blog post for details. Benno > also discussed the issue of the number of requests made. > > BTW: I've taken the public-html list off this thread, since I think > the discussion so far was only by WHATWG

Re: [whatwg] unexpected use of the CORS specification

Yes, that's the point. Please read the blog post for details. Benno also discussed the issue of the number of requests made. BTW: I've taken the public-html list off this thread, since I think the discussion so far was only by WHATWG members and we want to avoid too much cross-posting. Thanks, Si

Re: [whatwg] unexpected use of the CORS specification

I think that Silvia was implying that a URL shortening service could respond with Access-Control-Allow-Origin:*or some such header to signal to the browser that this domain serves resources in a cross-origin fashion. This would

Re: [whatwg] unexpected use of the CORS specification

I don't see the connection with CORS. The browser is free to request whatever URLs it wants. The results need not be accessible to content. Maybe I'm misunderstanding. Adam On Sat, Nov 7, 2009 at 11:35 PM, Silvia Pfeiffer wrote: > Hi, > > a friend of mine just wrote an interesting blog post

Re: [whatwg] unexpected use of the CORS specification

This could lead to a lot of requests being made by the client, just to check a url. If a page contains 100 links, then 100 HEAD requests need to be made, and in most cases they will be plain old ordinary links, so no 301 redirects. The browser could do the check when you mouse over the link, that i

[whatwg] unexpected use of the CORS specification

Hi, a friend of mine just wrote an interesting blog post about "unshortening twitter URLs", see http://benno.id.au/blog/2009/11/08/urlunshortener . In it he proposes that url shorteners should be treated specially in browsers such that when you mouse over a shortened url, the browse knows to inte