Opened 8 years ago

Closed 7 years ago

#320 closed design (fixed)

add advice on defining auth scheme parameters

Reported by: julian.reschke@… Owned by: draft-ietf-httpbis-p7-auth@…
Priority: normal Milestone: 17
Component: p7-auth Severity: Active WG Document
Keywords: Cc:

Description

When new schemes define new auth parameters, they of course need to stick to the base syntax.

In theory they *can* profile the allowable syntax, but doing so will not work well with consumers that use auth-scheme-agnostic parsers. It's thus best to define auth params based on what a parser would return *after* processing quoted-strings.

Attachments (1)

320.diff (2.1 KB) - added by julian.reschke@… 8 years ago.
Proposed patch

Download all attachments as: .zip

Change History (6)

comment:1 Changed 8 years ago by julian.reschke@…

  • origin set to http://www.w3.org/mid/4EA9B901.1070305@gmx.de

Changed 8 years ago by julian.reschke@…

Proposed patch

comment:2 Changed 8 years ago by julian.reschke@…

From [1465]:

Explain that new authentication schemes can not override the parsing rules for WWW-Authenticate with respect to param value syntax, and also add an example for a non-trivial to parse header field instance (see #320)

comment:3 Changed 8 years ago by julian.reschke@…

  • Milestone changed from unassigned to 17
  • Resolution set to incorporated
  • Status changed from new to closed

comment:4 Changed 7 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:5 Changed 7 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.