See TAP5-467, TAP5-468, TAP5-469.
2009/1/26 Patrick Moriarty
> My pleasure, most of the time ;)
>
> I'll create a couple of JIRA issues for these.
>
> Patrick
>
> 2009/1/23 Howard Lewis Ship
>
>> These all sound like issues that should be added to JIRA. Thanks for
>> hanging out on the bleedin
My pleasure, most of the time ;)
I'll create a couple of JIRA issues for these.
Patrick
2009/1/23 Howard Lewis Ship
> These all sound like issues that should be added to JIRA. Thanks for
> hanging out on the bleeding edge!
>
> On Fri, Jan 23, 2009 at 3:38 AM, Patrick Moriarty
> wrote:
> > I'
These all sound like issues that should be added to JIRA. Thanks for
hanging out on the bleeding edge!
On Fri, Jan 23, 2009 at 3:38 AM, Patrick Moriarty
wrote:
> I've resorted to returning a TextStreamResponse with
> "application/json" as the content type in order to bypass gzip
> compression.
>
I've resorted to returning a TextStreamResponse with
"application/json" as the content type in order to bypass gzip
compression.
2009/1/23 Patrick Moriarty :
> Looks like adding "application/json" to the configuration for
> ResponseCompressionAnalyzer doesn't quite do it because it's compared
> di
Looks like adding "application/json" to the configuration for
ResponseCompressionAnalyzer doesn't quite do it because it's compared
directly against "application/json;charset=UTF-8".
I could add "application/json;charset=UTF-8" but I think
ResponseCompressionAnalyzer should probably ignore the cha
Hi,
Since the recent introduction of gzip compression returning a
JSONObject from a mixin event method results in an empty responseText
in Firefox. It seems there is some problem with Content-Type:
application/json and Content-Encoding: gzip headers that prevents the
response from being decompres
