[OAUTH-WG] [oauth][RFC 5849] A question in example about the api
lvlin <lvlinster@gmail.com> Fri, 29 June 2012 03:14 UTC
Return-Path: <lvlinster@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A751011E811C for <oauth@ietfa.amsl.com>; Thu, 28 Jun 2012 20:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yq+-VjtxyBG3 for <oauth@ietfa.amsl.com>; Thu, 28 Jun 2012 20:14:16 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id D2EBA11E810D for <oauth@ietf.org>; Thu, 28 Jun 2012 20:14:15 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so4287349lbb.31 for <oauth@ietf.org>; Thu, 28 Jun 2012 20:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=yRUOVNm4K1UM3N0uoR37qImgWQ5QHsUdAPYn88+FxU0=; b=UTpiwCQYFBcIrPXmSP2xDVxgIt6II92hF9uXmnjyC5esj4yPa8kQyumFbSRyusQGVS K46XNk9/oTu5WF59KaKPK272YkIiR4al1KfQz+H1rGm/HR39yDc4JIwybRwwmy2jUqnF /9YWqBvBOP76cPnxJdCKxqs04u0/UgiTMW/VQG00SsR/7n1e0F1I33wEFQZCwDnTZHB7 n2n7H/CZ5wyx7xEsPfNbFZoe4DQL2EGZs5wfjblQKSBH5xrX4fGshEeYjcB9bqi9txuW UMWjPM+SShKNRAqKQhzTU9S2u4q2FyAl3xAK3rrffW4HEp3IZeCcxnl8vQeQCOFrL71W Qo0g==
Received: by 10.152.112.233 with SMTP id it9mr4632780lab.40.1340939654819; Thu, 28 Jun 2012 20:14:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.91.174 with HTTP; Thu, 28 Jun 2012 20:13:54 -0700 (PDT)
From: lvlin <lvlinster@gmail.com>
Date: Fri, 29 Jun 2012 11:13:54 +0800
Message-ID: <CAJXJZQ88=B+r2BP-1+L2YXZ0yp0aALKm4uiuB6unY0PGVfg3DA@mail.gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary="f46d040838d3ca6d9804c393d785"
Subject: [OAUTH-WG] [oauth][RFC 5849] A question in example about the api
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 03:15:57 -0000
Hi
I have a question in the example for section 1.2 in the OAuth 1.0 RFC 5849.
The example in the API calling to access the protected resource.
Where it reads:
With a set of token credentials, the client is now ready to request
the private photo:
GET /photos?file=vacation.jpg&size=original HTTP/1.1
Host: photos.example.net
Authorization: OAuth realm="Photos",
oauth_consumer_key="dpf43f3p2l4k3l03",
oauth_token="nnch734d00sl2jdk",
oauth_signature_method="HMAC-SHA1",
oauth_timestamp="137131202",
oauth_nonce="chapoH",
oauth_signature="MdpQcU8iPSUjWoN%2FUDMsK2sui9I%3D"
I don't know how does the client know the parameter value "vacation.jpg" in
the API "http://photos.example.net/photos". The question is, how does the
client can get the name(s) of protected resource? The use Jane gave it or
the server gave?
Best regards,
J. Lu