mace-opensaml-users - Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder
Subject: OpenSAML user discussion
List archive
- From: John Gonzales <>
- To:
- Cc: "Cantor, Scott E." <>
- Subject: Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder
- Date: Sat, 05 Feb 2011 12:16:15 -0600
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=PrJjpQ1fd8SLUSp6hGr9XEYqkNZHfXcBEsG8D6g9Y2TjGK+zArk+MfF+s8XwlanonX rejcDx/bII1maZsAlQLeIBmS3Glk6OFB+BySAanKE9DV9u/ZG7T7SOzB5+l+Gr5QGMc6 shnFjrbKCB0prDg02Lbo5hvxQSsFRZM3FJuo0=
On 11-02-05 12:09 PM, Cantor, Scott E. wrote:
Hi Scott,I thought I gave the OpenSAML API and other SAML documentation (i.e.,Maybe I'm not following...obviously issues with Ruby have nothing to do with
bindings, profiles, core, etc.) a good read, but I clearly missed something.
So I
am very curious, should/would I have been able to pick this information up
from either the two resources I just mentioned?
OpenSAML or SAML itself, but if you're saying that you weren't clear on the
format itself, that would be an issue for the SAML bindings specification. Is
there something you think wasn't clarified adequately?
-- Scott
Thanks for the response. I'm not sure if you're able to see my responses to the mailing list. Chris Card was able to resolve this issue for me. It had nothing to do with OpenSAML but rather the implementation of the ZLib C Library. By default, if you do not specify the appropriate bit size, then it Zlib::Inflate will use either GZip or ZLib, and not the raw DEFLATE format.
Documentation was poor on Zlib::Inflate. Chris Card was able to point this out to me because he had experienced the same issue before.
-jg.
- [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- RE: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, Chris Card, 02/05/2011
- Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- RE: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, Chris Card, 02/05/2011
- Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- RE: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, Chris Card, 02/05/2011
- Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- RE: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, Cantor, Scott E., 02/05/2011
- Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- RE: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, Cantor, Scott E., 02/05/2011
- Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- RE: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, Chris Card, 02/05/2011
- Re: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, John Gonzales, 02/05/2011
- RE: [OpenSAML] Unable to Decode message encoded by HTTPRedirectDeflateEncoder, Chris Card, 02/05/2011
Archive powered by MHonArc 2.6.16.