5 ms·
401 then 200 is part of kerberos/ntlm. You can watch it if you use curl -v 401 indicates it should send it's kerberos ticket. Kerberos verifies it should send
by Atotalnoob 3y ago
401 then 200 is part of kerberos/ntlm. You can watch it if you use curl -v
401 indicates it should send it's kerberos ticket.
Kerberos verifies it should send a ticket, then sends it.
200 cause you are now authenticated.
- gerdesj 3y agoYes, I know how it works but it fucks up log parsing. 401 is auth fail in http speak - https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401 https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401 401 does not indicate anything apart from authentication failure. Bear in mind that I am trying to parse logs to decide what is happening. I'm no expert but I suspect that http works a bit like this: C: hello web server S: yes I exist and I speak the following languages: lol, rofl, powershell (on thursdays) C: cool, let's talk lfor and I will sacrifice my first born child and give you my wallet S: no chance, but I speak lol and thank you for your wife C-S: witter on in "lol" for some time. <cat memes flow regardless> Kerberos has overloaded how auth should work and inadvertently fucked up log processing. Actually I think it is really NTLM. It goes in with auth instead of hello.