8274
75%
master: 37%

Ran 20 Jul 2018 04:24PM UTC

Jobs 1

Files 131

Run time 27s

Badge

Embed ▾

pending completion

Build # 8274

Build Type

Pull #2754

travis-ci

Committed by

web-flow

Commit Message

Only ever pick CURLAUTH_BEARER if we *have* a Bearer token

The Bearer authentication was added to cURL 7.61.0, but there is a
problem: if CURLAUTH_ANY is selected, and the server supports multiple
authentication methods including the Bearer method, we strongly prefer
that latter method (only CURLAUTH_NEGOTIATE beats it), and if the Bearer
authentication fails, we will never even try to attempt any other
method.

This is particularly unfortunate when we already know that we do not
have any Bearer token to work with.

Such a scenario happens e.g. when using Git to push to Visual Studio
Team Services (which supports Basic and Bearer authentication among
other methods) and specifying the Personal Access Token directly in the
URL (this aproach is frequently taken by automated builds).

Let's make sure that we have a Bearer token to work with before we
select the Bearer authentication among the available authentication
methods.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Pull Request Pull Request #2754: Only ever pick CURLAUTH_BEARER if we *have* a Bearer token

Run Details

13503 of 17368 relevant lines covered (77.75%)

848219.71 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
21	8274.21 (T=coverage)	20 Jul 2018 04:24PM UTC	269	75.53	Travis Job 8274.21

curl / curl / 8274
75%
master: 37%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 8274

curl / curl / 8274 75% master: 37%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 8274

curl / curl / 8274
75%
master: 37%

README BADGES
x