-------- Original-Nachricht -------- > Datum: Fri, 28 Aug 2009 11:59:15 +0200 > Von: Roland Olbricht <[email protected]> > An: [email protected] > Betreff: Re: [OSM-dev] Problem retrieving wiki pages
> > Of course, but the server (or more likely the proxy) is still > mis-behaving: > > if the client does not send an 'Accept-Encoding' header, the server must > > return plain text, not gzipped or deflated text. > > No. Have a look at the HTTP 1.1 specification > http://tools.ietf.org/html/rfc2616#section-14.3 > > "If no Accept-Encoding field is present in a request, the server MAY > assume that the client will accept any content coding." > If you read on, it also gives a recommendation for this case: "If no Accept-Encoding field is present in a request, the server MAY assume that the client will accept any content coding. In this case, if "identity" is one of the available content-codings, then the server SHOULD use the "identity" content-coding, unless it has additional information that a different content-coding is meaningful to the client." So you are right; strictly speaking, the behaviour of the proxy is not in violation of the RFC. However, it is recommended to use the identity encoding whenever possible. > If you think of a highly frequented server like the wiki, it's a good > decision > to compress the data whenever possible. I agree, but in this case the client gave no indication that it actually understands compressed replies. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
