From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (71-38-154-164.ptld.qwest.net [71.38.154.164]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 90C1578AD0 for ; Mon, 11 Aug 2014 07:10:22 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20140811094117.GC5637@toaster.adamthompson.me.uk> Date: Mon, 11 Aug 2014 07:09:26 -0700 In-Reply-To: <20140811094117.GC5637@toaster.adamthompson.me.uk> (Adam Thompson's message of "Mon, 11 Aug 2014 10:41:17 +0100") Message-ID: <87zjfbjey1.fsf@mushroom.PK5001Z> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] NTLM in edbrowse X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2014 14:10:23 -0000 Adam Thompson writes: > I also see no evidence of any kind of auth header during the requests. That's strange. No authentication header? Can you try using another browser that is known to work and comparing the headers that it receives and sends with the ones you are getting when trying to access the service with edbrowse? The lack of a WWW-Authenticate header makes me wonder if there could be some JS magic going on here as well. I honestly don't know anything about NTLM, except that it should be supported in libcurl. Lots of libcurl features are optional, and they can be disabled at the distro level. But NTLM support does not appear to be one of them. -- Chris