diff options
| author | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-02-22 16:41:01 +0000 |
|---|---|---|
| committer | cbentzel@chromium.org <cbentzel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-02-22 16:41:01 +0000 |
| commit | 5b9eb6cd8f4428c4647e1546aa2461d0062e0301 (patch) | |
| tree | d2ecf90ec66cfb7d1b6d3503f46973e9e4c381fe /sdch | |
| parent | 74d1423427b9665b5506e8fdc285597358ed3cf6 (diff) | |
| download | chromium_src-5b9eb6cd8f4428c4647e1546aa2461d0062e0301.zip chromium_src-5b9eb6cd8f4428c4647e1546aa2461d0062e0301.tar.gz chromium_src-5b9eb6cd8f4428c4647e1546aa2461d0062e0301.tar.bz2 | |
Validate that an SSPI scheme is supported before generating a handler.
When SSPI is used (for Windows builds), the NTLM and Negotiate handler
factories determine the maximum token length the first time it is used.
The SSPI call to determinine the maximum length also returns an error code
if the scheme is unsupported. The factories remember if the scheme is
unsupported and will not attempt to create any handlers. If the token length
is found, it is remembered. If a different error occurs, don't create a
handler this round, but try again in the future.
BUG=None
TEST=Manually used an incorrect auth scheme and validated that it worked. Working on a mock SSPI Library I can use for unit testing.
Review URL: http://codereview.chromium.org/600129
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39600 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sdch')
0 files changed, 0 insertions, 0 deletions