Forum Discussion
Koepp
4 years agoOccasional Visitor
Problem was with my settings, like I thought! Checking the "Authenciate Preemptively" check box in global HTTP settings solved the issue 🙂
- richie4 years agoCommunity HeroHey Koepp,
are you answering this or is this a separate issue or something else?
Reason why i ask, what i got from hananurrehman's message was that there were 2 Content-Length headers being generated in hia request and i wouldnt expect hitting authenticate preemptively checkbox to fix that...??
Ta
Rich- markhell1123 years agoNew Member
I got the error to go away (in SoapUI 4.5.1) by checking the Authenticate Preemptively flag in
Preferences -> HTTP Settings -> Authenticate Preemptively
Related Content
- 2 years ago
Recent Discussions
- 3 days ago