|
List Info
Thread: Re: About X-JSON header and evil things... ;)
|
|
| Re: About X-JSON header and evil
things... ;) |

|
2007-01-25 14:45:08 |
|
Hi, thanks for the feedback.
I'm working on a better handling of exceptions. Will post a patch asap.
Regarding x-json, I think we should leave it as it is for consitency
and backwards compatibility. It should also still be available if the
mime-type is set to application/json.
I had thaught about a global AJAX.sanitizeJSON option. It certainly
something we could implement at some point, but there are some
potential issues with that (especially if you rely on some third party
libs also using Prototype). Your best option for such cases is to
create a var holding your hash of options and reference it each time.
Thanks for the extended comment.
Cheers,
Tobie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs googlegroups.com
To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe googlegroups.com
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
|
| Re: About X-JSON header and evil
things... ;) |

|
2007-01-25 14:52:20 |
|
I think sanitizeJSON should be optional.. {sanitize: true}
my 2 cents.
On 1/25/07, tobie gmail.com> wrote:
>
> Hi, thanks for the feedback.
>
> I'm working on a better handling of exceptions. Will post a patch asap.
>
> Regarding x-json, I think we should leave it as it is for consitency
> and backwards compatibility. It should also still be available if the
> mime-type is set to application/json.
>
> I had thaught about a global AJAX.sanitizeJSON option. It certainly
> something we could implement at some point, but there are some
> potential issues with that (especially if you rely on some third party
> libs also using Prototype). Your best option for such cases is to
> create a var holding your hash of options and reference it each time.
>
> Thanks for the extended comment.
>
> Cheers,
>
> Tobie
>
>
> >
>
--
Kjell
-- www.m3nt0r.de
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs googlegroups.com
To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe googlegroups.com
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
|
| Re: About X-JSON header and evil
things... ;) |

|
2007-01-25 16:13:11 |
|
On 1/25/07, tobie gmail.com> wrote:
> I had thaught about a global AJAX.sanitizeJSON option. It certainly
> something we could implement at some point, but there are some
> potential issues with that (especially if you rely on some third party
> libs also using Prototype).
That would be only a problem, if the third party module depends on
evalJSON() to not only return an object, but to also execute some
commands contained in the data, which makes the data not a JSON
structure in the first place and it is then an error to call evalJSON.
Bye,
Martin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs googlegroups.com
To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe googlegroups.com
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
|
[1-3]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|