webcal should also be whitelisted.
James
On Sat, Apr 23, 2011 at 6:41 AM, timeless wrote:
>
> On Fri, Apr 22, 2011 at 1:07 AM, Michael A. Puls II
> wrote:
> > Besides mailto, these should be white-listed:
> >
> > mms
> > nntp
>
> news
>
> > rtsp
On Fri, Apr 22, 2011 at 1:07 AM, Michael A. Puls II
wrote:
> Besides mailto, these should be white-listed:
>
> mms
> nntp
news
> rtsp
On Tue, 19 Apr 2011 13:33:43 -0400, Ian Hickson wrote:
On Tue, 12 Apr 2011, Lachlan Hunt wrote:
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
[...]
We'd like to know if we've missed any important schemes that must be
b
On 4/20/2011 2:11 AM, Lachlan Hunt wrote:
On 2011-04-19 19:33, Ian Hickson wrote:
On Tue, 12 Apr 2011, Lachlan Hunt wrote:
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
[...]
We'd like to know if we've missed any impor
On 2011-04-19 20:29, Tab Atkins Jr. wrote:
On Tue, Apr 19, 2011 at 11:11 AM, Lachlan Hunt wrote:
I'm also curious how we could handle ISBN URNs, like:
urn:isbn:0-395-36341-1
That would be useful to have a web service that could look up the ISBN and
direct users to information about the book
On Tue, Apr 19, 2011 at 11:11 AM, Lachlan Hunt wrote:
> I'm also curious how we could handle ISBN URNs, like:
>
> urn:isbn:0-395-36341-1
>
> That would be useful to have a web service that could look up the ISBN and
> direct users to information about the book, or to an online store.
>
> As curre
On 2011-04-19 19:33, Ian Hickson wrote:
On Tue, 12 Apr 2011, Lachlan Hunt wrote:
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
[...]
We'd like to know if we've missed any important schemes that must be
blocked, and we th
On Tue, Apr 19, 2011 at 10:33 AM, Ian Hickson wrote:
> On Tue, 12 Apr 2011, Lachlan Hunt wrote:
> >
> > We are investigating registerProtocolHandler and have been discussing
> > the need for a blacklist of protocols to forbid.
> >
> > [...]
> >
> > We'd like to know if we've missed any important
On Tue, 12 Apr 2011, Lachlan Hunt wrote:
>
> We are investigating registerProtocolHandler and have been discussing
> the need for a blacklist of protocols to forbid.
>
> [...]
>
> We'd like to know if we've missed any important schemes that must be
> blocked, and we think it might be useful if
On Tue, Apr 12, 2011 at 5:18 PM, Lachlan Hunt wrote:
> We are investigating registerProtocolHandler and have been discussing the
> need for a blacklist of protocols to forbid.
>
> Our list currently includes:
> * http:
> * https:
> * ftp:
> * file:
>
> * about:
> * data:
>
> Email specific scheme
On 4/12/11, Lachlan Hunt wrote:
> On 2011-04-12 16:18, Lachlan Hunt wrote:
>> Ancient Netscape scripting schemes. some were apparently aliases for
>> javascript:
>> * mocha:
>> * livescript:
>> * livewire:
>> * tcl:
>
> Correction: tcl wasn't Netscape, it was some other minor browser. Not
> sure w
* Lachlan Hunt wrote:
Also, implementers need to be take care with vendor specific schemes:
* chrome: (Mozilla, Chrome)
We should probably block these too, for consistency.
* view-source: (Mozilla, Chrome)
This might have a valid use case in web-based editors like ACE:
http://ajaxorg.gi
On 2011-04-12 16:18, Lachlan Hunt wrote:
Hi,
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
Our list currently includes:
* http:
* https:
* ftp:
* file:
Also, blob:
Ancient Netscape scripting schemes. some were apparentl
Hi,
We are investigating registerProtocolHandler and have been discussing
the need for a blacklist of protocols to forbid.
Our list currently includes:
* http:
* https:
* ftp:
* file:
* about:
* data:
Email specific schemes:
* cid:
* mid:
Scripting schemes:
* javascript:
* vbscript:
Ancie
14 matches
Mail list logo
