edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] NTLM in edbrowse
Date: Mon, 11 Aug 2014 16:24:20 +0100	[thread overview]
Message-ID: <20140811152420.GB16817@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87zjfbjey1.fsf@mushroom.PK5001Z>

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

On Mon, Aug 11, 2014 at 07:09:26AM -0700, Chris Brannon wrote:
> Adam Thompson <arthompson1990@gmail.com> 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.

Ok, so it looks like (from running a couple of curl commands)
the problem is a libcurl one. Basically
when I use --ntlm the request with curl succeeds, however when I use --anyauth,
libcurl tries Negotiate which obviously fails since I haven't got it set up.
Since I suspect this is probably the case for almost everyone,
I'm tempted to make edbrowse tell libcurl only to do basic,
Digest and NTLM by default (testing with curl --basic --digest --ntlm works
against the service concerned).
We could then allow other auth methods in the config file. Any thoughts?

Cheers,
adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-08-11 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11  9:41 Adam Thompson
2014-08-11 14:09 ` Chris Brannon
2014-08-11 15:24   ` Adam Thompson [this message]
2014-08-11 21:25     ` Adam Thompson
2014-08-11 21:46 Karl Dahlke
2014-08-11 22:04 ` Adam Thompson
2014-08-11 22:25   ` Chris Brannon
2014-08-13  8:47     ` Adam Thompson
2014-08-14 20:25       ` Adam Thompson
2014-08-11 22:14 Karl Dahlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140811152420.GB16817@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chris@the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).