oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Sanso (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBER-64) QueryParameterApplier needs to include the scope parameter in the fragment
Date Fri, 11 Jan 2013 15:28:12 GMT

    [ https://issues.apache.org/jira/browse/AMBER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551169#comment-13551169

Antonio Sanso commented on AMBER-64:

Hi Stein,

thanks a lot for your effort and sorry if I have confused you. I put some extra thought into
it and I have realized I was wrong.

"The client MUST ignore unrecognized response parameters. "  if perfectly fine with our implementation.
Even if the response from the server has some extra parameter is the job of the client to
ignore it.

I will apply a patch more inline with your original first patch but I will also include the
error parameter in the fragment as for [1].

If you do not like the solution I am more than happy to discuss :)

Thanks again!!

[1] http://tools.ietf.org/html/rfc6749#section-
> QueryParameterApplier needs to include the scope parameter in the fragment 
> ---------------------------------------------------------------------------
>                 Key: AMBER-64
>                 URL: https://issues.apache.org/jira/browse/AMBER-64
>             Project: Amber
>          Issue Type: Bug
>            Reporter: Stein Welberg
>            Assignee: Antonio Sanso
>         Attachments: AMBER-64_improved.patch
> According to the spec (see [0]) the scope parameter also needs to be included in the
url fragment if it is provided.
> Please find the patch attached to fix this attached to this issue.
> [0] http://tools.ietf.org/html/rfc6749#section-4.2.2

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message