Jonathan Rosenberg wrote:
> No, no, no. Its the WWW-Authenticate and Proxy-Authenticate headers that
> are "collected", placed into a SINGLE 401 or 407, and forwarded upstream.
Jonathan:
The above is in reference to a forking proxy "collecting" multiple
WWW-Authenticate and Proxy-Authenticate headers and placing them into a
single 401 or 407 for delivery to the upstream UAC.
Now, should the bis say anything about how this "collection" is represented
in the single 401 (or 407) response? Multi-part MIME? Blank lines in the
body between each WWW-Authenticate/Proxy-Authenticate (with the Content-
Length field encompassing all the headers such collected)? As far as I
know, the bis does not make any mention of how these "collected" responses
are aggregated into one response body.
Any implementation experience out there?
Thanks,
- vijay
--
Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org}
Internet Software and eServices Group
Lucent Technologies/Bell Labs Innovations 263 Shuman Blvd., Rm 1A-413
Naperville, Illinois 60566 Voice: +1 630 224 0216 Fax: +1 630 713 0184
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
