Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-75
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Major Major
Assignee: dannycoward
Reporter: dannycoward
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
websocket-spec

Consider requiring BASIC and DIGEST authentication schemes in the client container.

Created: 14/Dec/12 11:09 PM   Updated: 26/Jan/13 12:16 AM  Due: 25/Jan/13   Resolved: 26/Jan/13 12:16 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags: v012
Participants: dannycoward


 Description  « Hide

as symopsis



dannycoward added a comment - 17/Jan/13 12:52 AM

Note that if we allow all client components to intercept the handshake, they have the ability to provide their own implementations of BASIC and DIGEST (and any number of other Http request/response authentication schemes) without having to require them in all implementations.


dannycoward added a comment - 26/Jan/13 12:15 AM

We will not support this for version 1.0.

Am closing this issue and adding it to the wishlist for the next version.


dannycoward added a comment - 26/Jan/13 12:16 AM

will consider for next version.