Forum Discussion
jsmith_83470
Nimbostratus
Sep 08, 2009Super HTTP and NTLM
Hi folks,
I'm curious if anyone has managed to get the Super HTTP Monitoring working with NTLM. My understanding is that because the when authentication is required the first HTTP response is a 401 (followed by the 'browser' sending NTLM credentials then returning a 200) that the script does not work because of the following line:
local actual_status_code=$(head -n 1 "$tmpfile" | sed "s/^HTTP\/.\.. \([0123456789][0123456789][0123456789]\) .*$/\1/")
[ -n "$status_code" ] && [ "$actual_status_code" -ne "$status_code" ] && fail \
I tried doing a grep on HTTP/1.1 but this seems to result in the pool always staying up even if the wrong credentials are sent so I'm guessing that I'm missing something here.
I'm curious how other folks are handling this either with the Super HTTP script (which is nice because of its portability, if it works) or whether there is another script that I haven't come across.
Looking forward to some responses
Thanks,
J
No RepliesBe the first to reply
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects