here's the current diff against trunk to remove those X's. :)
diff -r 5d9a66496e58 gluon/http.py
--- a/gluon/http.py Fri Feb 22 10:18:58 2013 -0600
+++ b/gluon/http.py Fri Feb 22 12:50:11 2013 -0800
@@ -97,9 +97,6 @@
if not body:
body = status
if
If no objection I will remove those.
On Saturday, 15 December 2012 08:12:24 UTC-6, Niphlod wrote:
>
> nope. I'm +1 on all the line "remove those characters".
> My point was to eliminate that from http alltogether, or (but it will
> require more checks) remove that from restful AND @service calls.
nope. I'm +1 on all the line "remove those characters".
My point was to eliminate that from http alltogether, or (but it will
require more checks) remove that from restful AND @service calls.
On Saturday, December 15, 2012 12:50:17 AM UTC+1, howesc wrote:
>
> is anybody using request.restful *and
is anybody using request.restful *and* needs the 512 bytes in a restful
response? i'm inclined to only skip those bytes for restful requests
(because they are usually not displayed by browsers).
thanks,
cfh
On Friday, December 14, 2012 2:48:39 PM UTC-8, Niphlod wrote:
>
> Please... let be sur
Please... let be sure that those injected characters are going to be
replied only to a browser request, possibly only IE. Technically as long as
the gzipped body stays over 512 byte IE will show the page.
Lets not forget, plase, that the thread started requesting to delete
those nasty 512
This is a problem. How about injecting more characters instead of less. How
about an image encoded in ascii?
On Friday, 14 December 2012 13:44:24 UTC-6, Niphlod wrote:
>
> problem with older browser is : retrieve a working copy of it.
> However, http://core.trac.wordpress.org/ticket/8942 and
problem with older browser is : retrieve a working copy of it.
However, http://core.trac.wordpress.org/ticket/8942 and the following
http://www.clintharris.net/2009/ie-512-byte-error-pages-and-wordpress/,
http://support.microsoft.com/kb/294807 seems to point in the direction of <
7.
Others s
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 >
> wrote:
>
> Just to report, the problem is not "fixed" for many
On 14 Dec 2012, at 8:28 AM, Niphlod 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 compressionI guess however for
> production sites ev
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 compressionI guess however for
production sites everyone has his custom page and not the default one.
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
11 matches
Mail list logo
