-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Minor
-
None
-
Affects Version/s: 2.0
-
Component/s: Metadata
-
None
http://lists.oasis-open.org/archives/security-services/200501/msg00058.html
The HTTP-Redirect binding in theory allows for alternate message encoding mechanisms into the URL, but the metadata support for the binding has no facility for indicating what encoding(s) an endpoint supports. This becomes an issue if other encodings are proposed.
It was a PE but was moved to the "issues list" back in 2005.