support for gzip/deflate compression of fetched metadata
Tom Scavo
trscavo at gmail.com
Sun Aug 21 20:28:10 BST 2011
On Sun, Aug 21, 2011 at 12:26 PM, Chad La Joie <lajoie at itumi.biz> wrote:
> On Aug 21, 2011, at 11:58 AM, Tom Scavo wrote:
>
>> This is just a reality check. From the documentation, it appears both
>> IdP 2.2 (and later) and SP 2.4 (and later) support gzip/deflate
>> compression of fetched metadata. Is this correct?
>>
>> I checked a handful of federations and none seems to support HTTP
>> compression. Does anyone know of a federation that supports this?
>>
> That is correct for the IdP.
Thanks.
> I don't know of any federations that use it currently but has talked about turning it on for the UK. They already have proper ETag and Last-Modified support.
That was going to be my next question. So, IdP 2.2 (and later)
supports HTTP conditional GET (ETag and Last-Modified in the response,
and If-None-Match in the request) as well as HTTP compression
(Accept-Encoding in the request and Content-Encoding in the response).
Is that correct?
In the request, what exactly is the value of the Accept-Encoding header?
Tom
More information about the users
mailing list