<div dir="ltr"><div>Of course you are absolutely right. Just after sending the e-mail I checked the standard documents again and recognized my error. Sorry.</div><div><br></div><div>I was mislead by the form <a href="https://www.samltool.com/decode.php">https://www.samltool.com/decode.php</a> </div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-24 19:03 GMT+01:00 Brent Putman <span dir="ltr"><<a href="mailto:putmanb@georgetown.edu" target="_blank">putmanb@georgetown.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<p><br>
</p>
<br>
<div class="m_7328156787288136481moz-cite-prefix">On 3/24/17 3:13 AM, Axel Rose wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div>Using OpenSAML3 and HTTPPostEncoder I get a seemingly
corrupt (*) AuthNRequest.</div>
<div>The request ist fine though if I use
HTTPRedirectDeflateEncoder.</div>
<br>
</div>
</blockquote>
<br></span>
Well, if per the subject line, you're expecting the POST encoder to
deflate the SAML message: That's incorrect. In the SAML 2 POST
binding, there is no deflation like in the Redirect-DEFLATE
binding. The serialized XML is simply base64-encoded and placed
into the form. SAML Bindings, section 3.5.4:<br>
<br>
<blockquote type="cite">Messages are encoded for use with this
binding by encoding the XML into an HTML form control and are<br>
transmitted using the HTTP POST method. A SAML protocol message is
form-encoded by applying the<br>
base-64 encoding rules to the XML representation of the message
and placing the result in a hidden form<br>
control within a form as defined by [HTML401] Section 17. ......<br>
</blockquote>
<br>
</div>
<br>--<br>
To unsubscribe from this list send an email to <a href="mailto:dev-unsubscribe@shibboleth.net">dev-unsubscribe@shibboleth.net</a><br></blockquote></div><br></div>