Http PreAuthenticate problem

0 votes
asked Dec 1, 2018 by lanopk (1,550 points)


I am now in a little serious condition.
I changed all exist Http to Rebex.
However, too many 401 response and all upload failures occurred.

Request.PreAuthenticate does not seem to affect other requests.

In the case of the default HttpWebRequest, even if a new HttpWebRequest is created, it does not generate a 401 error because it is processed using the existing authentication.

Each Rebex http request receives a 401 error.

What should I do with Request.PreAuthenticate to handle multiple requests at the same time?

And this is causing upload problems.

When uploading very large files, using 'AllowWriteStreamBuffering = false' will cause an error because of 401 error.

This is normal error, but I believe this problem will be solved if PreAuthentication works properly.

Can you provoide PreAuthenticate related functionality in HttpRequestCreator?

Thank you.

Applies to: Rebex HTTPS
commented Dec 1, 2018 by lanopk (1,550 points)
And, if WebDAV Server require only Digest Authentication,
this cause exception error : Server requires authentication, but none of the authentication methods is supported or allowed.

1 Answer

0 votes
answered Dec 3, 2018 by Lukas Matyska (60,730 points)


The PreAuthentication feature is not supported yet, but it is very easy to add this to the current version. I will do it now. If you want to receive BETA version, please let me know.

The Digest authentication is not supported. Unfortunately, it is not so easy. We will add it in one of future versions.

commented Dec 3, 2018 by lanopk (1,550 points)
Thank you.
I did rollback all files.
I will wait for the next release.
(http PreAuthentication, Digest Auth(NTLM Auth), WebSocket Client(socks5) etc)
commented Mar 14, 2019 by anonymous

Is the PreAuthentication feature already in 2018-12-21 Version 2018 R4?
commented Mar 14, 2019 by Lukas Matyska (60,730 points)
No, it is planned for next public release 2019 R1, which is coming soon.