- From: Mark Nottingham <mnot@mnot.net>
- Date: Mon, 4 Jun 2012 10:45:47 +1000
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, HTTP Working Group <ietf-http-wg@w3.org>
On 02/06/2012, at 8:30 PM, Julian Reschke wrote: > On 2012-06-01 02:50, Mark Nottingham wrote: >> >> On 31/05/2012, at 11:59 PM, Stephen Farrell wrote: >>>> """ >>>> Both the Authorization field value and the Proxy-Authorization field value contain the client's credentials for the realm of the resource being requested, based upon a challenge received from the server (possibly at some point in the past). When creating their values, the user agent ought to do so by selecting the challenge with what it considers to be the most secure auth-scheme that it understands, obtaining credentials from the user as appropriate. >>>> """ >>> >>> Could be a can of worms so feel free to ignore me >> >> I suspect it's a bit of one. >> >>> but is >>> the term credentials there correct? Perhaps authenticator >>> would be better? If we do manage to get better schemes >>> defined then someday not all of these would allow derivation >>> of an underlying password credential. >> >> >> How about a nice generic "details", as in "obtaining details from the user as appropriate."? >> ... > > -1; if we change the terms we should do so consistently. I thought "details" captured a certain vagueness that would help in this particular case. YMMV. -- Mark Nottingham http://www.mnot.net/
Received on Monday, 4 June 2012 00:46:18 UTC