Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
211 user(s) are online (51 user(s) are browsing Forums)

Members: 0
Guests: 211

more...

Headlines

 
  Register To Post  

OWB and gzip doesn't work
Quite a regular
Quite a regular


See User information
I noticed a bug in OWB when visiting this page: www.turnetransport.se

In IB (which doesn't request gzip data) it displays fine but OWB only displays binary garbage, no page at all and it is because OWB announces that it can handle gzip (Accept-Encoding: deflate, gzip) but it obviously can't handle it when it gets it (Content-Encoding: , gzip, gzip) but displays raw binary instead.

Edit: This is OWB 3.23 for OS4.

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top
Re: OWB and gzip doesn't work
Home away from home
Home away from home


See User information
@Deniil

The page works with AWeb ( the relavence being that AWeb <b>does</b> support gzip encoding) so looks like it's a bug in OWB not the webpage...

Go to top
Re: OWB and gzip doesn't work
Home away from home
Home away from home


See User information
@broadblues

here are the returned headers:

GET HTTP/1.0
User
-AgentAmiga-AWeb/3.5.09 (0.167APL beta)
Accept: */*;q=1
Accept-Encoding: gzip
Host: www.turnetransport.se

HTTP/1.1 200 OK
Date: Sun, 21 Mar 2010 21:36:54 GMT
Server: Apache/2.2.3 (Debian) PHP/5.2.0-8+etch16 mod_ssl/2.2.3 OpenSSL/0.9.8c
X-Powered-By: PHP/5.2.0-8+etch16
Set-Cookie: PHPSESSID=5720c49bb95cc9df39e5ddb3878faff9; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Encoding: gzip
Content-Length: 7066
Connection: close
Content-Type: text/html;charset=iso-8859-1

Go to top
Re: OWB and gzip doesn't work
Just popping in
Just popping in


See User information
The headers returned are the same for IBrowse 2.4 too, which does have gzip encoding support (unless disabled in the prefs).

Go to top
Re: OWB and gzip doesn't work
Quite a regular
Quite a regular


See User information
@broadblues

The headers with OWB are slightly different since it also requests deflate:

GET HTTP/1.1
Host
www.turnetransport.se
Accept
-Encodingdeflategzip
Cookie
PHPSESSID=d2a65964fcd933f509b5f4c239a2f35a
User
-AgentMozilla/5.0 (compatibleOrigyn Web BrowserAmigaOS 4.1UenAppleWebKit/532.8+ (KHTMLlike GeckoSafari/532.8+)
Acceptapplication/xml,application/xhtml+xml,text/html,text/plain,image/png,*/*
Accept-Language: en-US, *


HTTP/1.1 200 OK
Date
Sat20 Mar 2010 15:57:04 GMT
Server
Apache/2.2.3 (DebianPHP/5.2.0-8+etch16 mod_ssl/2.2.3 OpenSSL/0.9.8c
X
-Powered-ByPHP/5.2.0-8+etch16
Expires
Thu19 Nov 1981 08:52:00 GMT
Cache
-Controlno-storeno-cachemust-revalidatepost-check=0pre-check=0
Pragma
no-cache
Content
-Encoding: , gzipgzip
Vary
Accept-Encoding
Content
-Length7089
Content
-Typetext/html;charset=iso-8859-1


Could it be this string: Content-Encoding: , gzip, gzip
starting with a comma that is confusing OWB? Or can it simply not handle gzip data properly?

Software developer for Amiga OS3 and OS4.
Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Go to top
Re: OWB and gzip doesn't work
Just popping in
Just popping in


See User information
@Deniil

Maybe it confuses it indeed (or CURL), because OWB certainly handles other gzipped pages.

Go to top
Re: OWB and gzip doesn't work
Just popping in
Just popping in


See User information
@Deniil

Yes, it is a server bug. It looks like the server has double gzipped the content for some reason, so when OWB unzipped the result is still a gzip stream. Probably the server does not recognise "deflate" because...

FYI, IBrowse normally sends:

Accept-Encoding: gzip, deflate

and receives:

Content-Encoding: gzip

But, after changing IBrowse to send:

Accept-Encoding: deflate, gzip

just like OWB does, then IBrowse encounters the same problem:

Content-Encoding: , gzip, gzip

Along with binary jibberish being displayed.

Go to top
Re: OWB and gzip doesn't work
Amigans Defender
Amigans Defender


See User information
@Futaura

Quote:

Futaura wrote:
Probably the server does not recognise "deflate" because...


...the spec was not implemented as intended by certain web server software, leading to nobody really knowing what they ought to be sending or receiving when it is specified?

Go to top
Re: OWB and gzip doesn't work
Just popping in
Just popping in


See User information
@Chris

Oh, I dunno... the RFCs are actually pretty clear on this. Although I remember cases of servers sending gzip encoded data anyway, even when the client did not say it could support that, but that's something different obviously.

I doubt Apache itself is at fault in this case, and it's most likely a site specific mis-configuration of Apache, it's modules and/or a PHP script issue that is causing the Content-Encoding header to get mangled. Can't really blame OWB just because it is sending the accepted encodings in a different order than "expected" by the site - in theory clients are allowed to use whatever ordering they want.

Go to top
Re: OWB and gzip doesn't work
Amigans Defender
Amigans Defender


See User information
@Futaura

Apache is probably behaving correctly wrt defalte encoding, it was our friends at Microsoft who misinterpreted the spec and IIRC treated deflate the same as gzip (deflate should be gzip data without the gzip header). As such, deflate is not to be trusted and accept-encoding: deflate is horribly unpredictable.

OWB is sending the right headers, the server will be probably using the first in the list it can handle - ie. "deflate" (with no weighting on them I have a feeling the server can choose, but if not the first will be used).

I'd be interested to see if Accept-encoding: deflate only (no gzip at all) also causes the server to return the dodgy encoding which, as you say, is most likely set by a PHP script or module.

Go to top
Re: OWB and gzip doesn't work
Just popping in
Just popping in


See User information
@Chris

Just tried with "Accept-Encoding: deflate" and the server returned uncompressed text. Although it also returned an empty "Content-Encoding: " header - don't think that is quite right either.

Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project