On Mon, Nov 9, 2009 at 12:35 PM, Maciej Stachowiak <[email protected]> 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 proposal at the link was for a method to do URL unshortening as a > client-side script in the browser. That would indeed require CORS. A feature > built-in to the browser would not.
Yes, there are different ways to solve this and we can go all the way to the browser, or leave it to a script. But to push it to a script (which I think is preferable), we need CORS. Cheers, Silvia.
