I thought this was a problem with IE7 too. If we know for sure this is only
IE6 problem, I am ok with removing that code.
On Friday, 14 December 2012 10:40:20 UTC-6, Jonathan Lundell wrote:
>
> On 14 Dec 2012, at 8:28 AM, Niphlod <nip...@gmail.com <javascript:>>
> wrote:
>
> Just to report, the problem is not "fixed" for many production
> environments even with that trick.... If gzip compression is done by the
> webserver, the response must be > 512 bytes after the compression....I
> guess however for production sites everyone has his custom page and not the
> default one.
>
> Anyway, using web2py as a backend (as in restful requests, @service calls,
> etc), can't we just leave out that trick and add 512 bytes to the default
> error ticket view ? After all, it's only a problem of IE < 7
>
>
> Are we really trying to support IE6?
>
>
>
> On Friday, December 14, 2012 4:52:35 PM UTC+1, Massimo Di Pierro wrote:
>>
>> Older versions of IE will override the error page and display an IE error
>> page is the length is less than 512.
>> As far as I know it is still relevant to display web2py error tickets on
>> older IE browsers.
>>
>> On Thursday, 13 December 2012 17:48:19 UTC-6, howesc wrote:
>>>
>>> in http.py there exists this block:
>>>
>>> if isinstance(body, str):
>>> if len(body) < 512 and \
>>> headers['Content-Type'].startswith('text/html'):
>>> body += '<!-- %s //-->' % ('x' * 512) # trick IE
>>>
>>>
>>> when i'm using request.restful i don't necessarily want all of those
>>> X's......would it be ok for me to make a patch that skips this block in a
>>> restful request? (is this IE hack still relevant?)
>>>
>>> thanks!
>>>
>>> christian
>>>
>>
>
>
>
>
--
