On Sun, 2008-07-20 at 19:44 +0200, Iñaki Baz Castillo wrote: > Hi, let me a stupid question: > If the challenge header is called "WWW-Authenticate" > or "Proxy-Authenticate"... why the request response header is > called "Authorization" and "Proxy-Authorization"? wouldn't make more > sense "Authentication" (better "WWW-Authentication") > and "Proxy-Authentication"? > > Thanks. > > PD: Please, don't redirect me to RFC 2617 authors since SIP authors could > choose to change/improve the specification.
Being able to use exactly the same code for HTTP and SIP is pretty handy. As for why it was done that way in HTTP, it was already a deployed system with a poorly chosen name before the spec was created (at least before any IETF spec was created), and preserving some level of backward compatibility was considered far more important than getting a distinction correct in the label choice. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
