[EMAIL PROTECTED] wrote:
Hi folks,
we need to figure out what is really needed.
A big requirement is security. It must not be possible to connect to an
arbitrary port on the server and send anything, unless the server has
explicitly stated that it allows so using some sort of white-listing
Hi folks,
we need to figure out what is really needed.
--
Charles McCathieNevile, Opera Software: Standards Group
hablo español - je parle français - jeg lærer norsk
[EMAIL PROTECTED] Catch up: Speed Dial http://opera.com
On 5/30/07 12:04 PM, "Anne van Kesteren" <[EMAIL PROTECTED]> wrote:
>> It turned out that there is already some code (Dashboard widgets) that
>> relies on Http-Equiv METAs being honored by XMLHttpRequest. This worked
>> in shipping Safari/WebKit by accident: all XHR content was passed
>> through
On Wed, 30 May 2007 09:44:41 +0200, Alexey Proskuryakov
<[EMAIL PROTECTED]> wrote:
It turned out that there is already some code (Dashboard widgets) that
relies on Http-Equiv METAs being honored by XMLHttpRequest. This worked
in shipping Safari/WebKit by accident: all XHR content was passed
On 2/26/07 3:21 PM, "Anne van Kesteren" <[EMAIL PROTECTED]> wrote:
>> In my testing, I have found that existing implementations already deduce
>> the charset for XHR response in a way that's drastically different from
>> normal page loading.
>
> But should we really make it be like that? Once HT
