Per-Entity Metadata Working Group

[Tom Scavo <>]

This may come as a surprise but the apache server on md.incommon.org
is not configured for HTTP Compression. Ops has discussed this
occasionally over the years but the case for HTTP Compression has
never been compelling so we let it drop each time. Maybe it's time to
revisit.

First, I assume this is the right WG to have this discussion since
HTTP Compression is yet another marginal improvement like the IdP-only
aggregate. If you disagree, that's okay, just let me know and I'll
find another venue.

I don't know what metadata clients support HTTP Compression. I assume
Shibboleth does but I don't know that for a fact.

Assuming Shibboleth handles HTTP Compression just fine, I wouldn't
expect too many problems if we enabled apache but a few deployments
will experience problems, I'm sure. The fallback aggregate would come
in handy here. Does anyone know how to configure apache such that the
fallback aggregate is NOT compressed on the fly (yet everything else
is)?

If you have any other thoughts on this issue, let me know.

Thanks,

Tom