This is the simple fix of just adding type to blacklist. Is it time to ...
15 years, 10 months ago
(2010-02-25 23:39:39 UTC)
#2
This is the simple fix of just adding type to blacklist.
Is it time to revisit this and run the encoding detector only on text/html or
text/* instead of using blacklist?
This change looks fine as-is, but I agree that a whitelist approach is preferable. I'd ...
15 years, 10 months ago
(2010-02-26 01:09:58 UTC)
#3
This change looks fine as-is, but I agree that a whitelist approach is
preferable. I'd start with "text/*" as you mentioned. We might also want to
pass Mime type to the encoding detector in such case as we want more
fine-grained control over certain detection passes (eg. HTML-based).
On Thu, Feb 25, 2010 at 3:39 PM, <zhoresh@gmail.com> wrote:
> This is the simple fix of just adding type to blacklist.
>
> Is it time to revisit this and run the encoding detector only on
> text/html or text/* instead of using blacklist?
>
>
>
>
> http://codereview.appspot.com/224064/show
>
Why was image/x-icon added to the blacklist, but not: image/vnd.microsoft.icon, image/ico, image/icon, text/ico, application/ico On ...
15 years, 10 months ago
(2010-02-26 02:19:50 UTC)
#5
Why was image/x-icon added to the blacklist, but not: image/vnd.microsoft.icon,
image/ico, image/icon, text/ico, application/ico
On 2010/02/25 23:39:39, zhoresh wrote:
> This is the simple fix of just adding type to blacklist.
>
> Is it time to revisit this and run the encoding detector only on text/html or
> text/* instead of using blacklist?
Because that's the particular use case we saw in our logs resulting in uncaught exceptions ...
15 years, 10 months ago
(2010-02-26 07:23:54 UTC)
#6
Because that's the particular use case we saw in our logs resulting in
uncaught exceptions :)
IMO your examples call for changing the blacklist to whitelist as discussed.
See any noteworthy issues w/ that option?
Thanks,
John
On Thu, Feb 25, 2010 at 6:19 PM, <chiragshah1@gmail.com> wrote:
> Why was image/x-icon added to the blacklist, but not:
> image/vnd.microsoft.icon, image/ico, image/icon, text/ico,
> application/ico
>
>
> On 2010/02/25 23:39:39, zhoresh wrote:
>
>> This is the simple fix of just adding type to blacklist.
>>
>
> Is it time to revisit this and run the encoding detector only on
>>
> text/html or
>
>> text/* instead of using blacklist?
>>
>
>
>
> http://codereview.appspot.com/224064/show
>
Ah, got it. +1 to a whitelist On 2010/02/26 07:23:54, johnfargo wrote: > Because that's ...
15 years, 10 months ago
(2010-02-26 18:35:55 UTC)
#7
Ah, got it. +1 to a whitelist
On 2010/02/26 07:23:54, johnfargo wrote:
> Because that's the particular use case we saw in our logs resulting in
> uncaught exceptions :)
>
> IMO your examples call for changing the blacklist to whitelist as discussed.
> See any noteworthy issues w/ that option?
>
> Thanks,
> John
>
> On Thu, Feb 25, 2010 at 6:19 PM, <mailto:chiragshah1@gmail.com> wrote:
>
> > Why was image/x-icon added to the blacklist, but not:
> > image/vnd.microsoft.icon, image/ico, image/icon, text/ico,
> > application/ico
> >
> >
> > On 2010/02/25 23:39:39, zhoresh wrote:
> >
> >> This is the simple fix of just adding type to blacklist.
> >>
> >
> > Is it time to revisit this and run the encoding detector only on
> >>
> > text/html or
> >
> >> text/* instead of using blacklist?
> >>
> >
> >
> >
> > http://codereview.appspot.com/224064/show
> >
>
Issue 224064: Add image/x-icon to Blacklisted types from encoding detection
Created 15 years, 10 months ago by zhoresh
Modified 15 years, 10 months ago
Reviewers: shindig.remailer_gmail.com, johnfargo, chirag
Base URL: http://svn.apache.org/repos/asf/shindig/trunk/
Comments: 0