Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As far as I understand WebRequest.PreAuthenticate is almost always good.
If I enable it even when there is no credential it won’t try to authenticate, if there is a credential it’ll. So is there any legitimate reason to set it False? Or is it OK to set it True even when there is no credentials?
And since it’s quite useful why it’s not enabled by default just like many other HTTP features?
Rick Strahl has a very detailed blog post about this.
To summarize, if you need to be able to change the credentials in the request at some point (without the server intervention), do not set PreAuthenticate to true. Otherwise, go for it.