edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] NTLM in edbrowse
Date: Mon, 11 Aug 2014 15:25:08 -0700	[thread overview]
Message-ID: <87iolyk6kb.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140811220405.GE16817@toaster.adamthompson.me.uk> (Adam Thompson's message of "Mon, 11 Aug 2014 23:04:05 +0100")

Adam Thompson <arthompson1990@gmail.com> writes:

> Thanks, commit pushed.

Sounds good.  I'd still love to know why the auth negotiation is broken.
Is it something that needs to be reported upstream to the curl people?

The realm field from auth.c doesn't seem to be used after we switched
over to letting libcurl handle authentication.

-- Chris

  reply	other threads:[~2014-08-11 22:26 UTC|newest]

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

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=87iolyk6kb.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.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).