OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (SECURITY-2) ISSUE: URL encodingsupported by HTTP-Redirect endpoint



     [ http://tools.oasis-open.org/issues/browse/SECURITY-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor updated SECURITY-2:
--------------------------------

    Description: 
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.

  was:
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.


> ISSUE: URL encoding supported by HTTP-Redirect endpoint
> -------------------------------------------------------
>
>                 Key: SECURITY-2
>                 URL: http://tools.oasis-open.org/issues/browse/SECURITY-2
>             Project: OASIS Security Services (SAML) TC
>          Issue Type: New Feature
>          Components: Metadata
>    Affects Versions: Version 2.0
>            Reporter: Scott Cantor
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]