oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stein Welberg (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OLTU-185) OAuthClientResponse lack headers access to be used for correct RESTful client implementation
Date Mon, 22 Feb 2016 21:49:18 GMT

     [ https://issues.apache.org/jira/browse/OLTU-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stein Welberg resolved OLTU-185.
--------------------------------
    Resolution: Fixed

A headers object is now exposed in the OauthResourceResponse object containing all the response
headers

> OAuthClientResponse lack headers access to be used for correct RESTful client implementation
> --------------------------------------------------------------------------------------------
>
>                 Key: OLTU-185
>                 URL: https://issues.apache.org/jira/browse/OLTU-185
>             Project: Apache Oltu
>          Issue Type: Bug
>          Components: oauth2-client
>            Reporter: Vincent Amadou
>            Assignee: Stein Welberg
>              Labels: newbie++
>
> If I use OAuthClient to access a protected resource, more precisely to PUT a new resource,
I expect to receive a response object allowing me to get the Location header in the response.

> At this moment I can't access this header, simply because the OAuthClientResponse (and
more precisely OAuthResourceResponse) object are not exposing headers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message