Can't use header `Authorization` with no challenge scheme

[templth]

It seems that it's not possible to use an header Authorization with the following format:

Authorization: myToken

Challenge scheme seems mandatory (see AuthenticatorUtils#formatRequest):

Authorization: SCHEME something

Moreover from version 2.3.2, we can't define anymore the header using custom headers:

Addition of the standard header "Authorization" is not allowed.

See following question on StackOverflow: http://stackoverflow.com/questions/30576374/restlet-client-use-authentication-key/.

[thboileau]

Having a look at the HTTP RFC, it appears that the Authorization header should (perhaps must) mention the scheme (cf https://tools.ietf.org/html/rfc7235#page-4).
It appeared that some versions of the Restlet Framework allowed to specify the values of the so-called "standard" headers such as authorization. This was a regression fixed by this commit (44afd97) and shipped with 2.3.2.

[thboileau]

One workaround is to use an "empty" challenge scheme:

        ClientResource cr = new ClientResource("http://localhost:8182/");
        ChallengeResponse c = new ChallengeResponse(new ChallengeScheme("", ""));
        c.setRawValue("1234");
        cr.setChallengeResponse(c);

[danvass]

@thboileau Is this fixed in any of the new versions? Empty challengescheme is apparently not supported either.