Hi Paul,
Start here and see the linked RFCs.
https://en.wikipedia.org/wiki/Digest_access_authentication
I probably have some old code somewhere that implemented this, I'll see if I
can dig it up and send it to you.
John DeSoi, Ph.D.
> On Sep 29, 2019, at 11:42 AM, Paul Lovejoy wrote:
>
>
Hi John,
Thanks for your input. I wouldn’t know where to begin creating the
authentication digest myself. Can you point me somewhere?
Cheers,
Paul
> Le 27 sept. 2019 à 20:27, John DeSoi via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> Using a HTTP tracing tool where you could see all of
are you sure it is HTTP Get that is throwing the error?
the command is not supposed to touch the body
unless you pass OBJECT and the content type is application/json
or you pass PICTURE and the content type is image/*,
or you pass TEXT and the content type is text/*
https://doc.4d.com/4Dv17/4D/17
Using a HTTP tracing tool where you could see all of the request/response
values with headers might provide useful clues. My other idea would be to drop
HTTP AUTHENTICATE and just build the authentication digest headers yourself.
John DeSoi, Ph.D.
> On Sep 27, 2019, at 12:47 PM, Paul Lovejoy
Hi John,
Thanks for your feedback. I’m passing “2” in the extra parameter. The following
HTTP get() is returning an error -9935, badly formed XML. The HTTP get is
supposed to be retrieving XML, actually. So the error is not totally off base.
But I would prefer to know that authentification fail
The documentation says:
> If you omit the authMethod parameter (or pass 0), you let the program choose
> the appropriate method to use. In this case, 4D sends an additional request
> in order to negotiate the authentication method.
Are you omitting the authMethod parameter? If so, I suspect the
ists.4d.com>
Cc: Paul Lovejoy
Subject: HTTP AUTHENTICATE - how to know if the authentification worked
Hi everyone,
I’m using HTTP AUTHENTICATE to authenticate connections to a web server.
The call to authenticate is immediately followed by a HTTP get(). The HTTP get
occasionally fai
Hi everyone,
I’m using HTTP AUTHENTICATE to authenticate connections to a web server. The
call to authenticate is immediately followed by a HTTP get(). The HTTP get
occasionally fails and I’ve been able to trace this to a failed HTTP
AUTHENTICATE, which appears to be an error from the website.
8 matches
Mail list logo