You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing I identified an topic that runs into an error by using the wrapper. I'm using the SampleWdpClient app and randomly during request to the device, the device responses a request with a 307 state code and the wrapper follows the redirected uri an gets an html page as answer. As result, the deserializer fails because the answer isn't an json string.
In the most of the request, the device answers the request with an 401, the httpclient sends the credentials and all works well. Except in some cases (all 2-4 times) the device answers with an 307 and the wrapper fails.
Do I have to configure the devices differently (I tested more than one with the same result) ?
I'm using the last nuget version (0.9.5.1)
below the wireshark trace:
thanks a million.
The text was updated successfully, but these errors were encountered:
Hi @haeberle , are you using this against an IoT device? If so, we've identified the issue and are working to fix it in the WDP product itself.
The root cause here is that the .NET framework for HTTP purposefully sends the request without credentials, then responds with creds on a 401. Unfortunately the IoT Authenticator module in WDP counts cred-less requests as bad faith login attempts and ticks up a counter to mark whether they should be redirected to the login page.
Dear team
During testing I identified an topic that runs into an error by using the wrapper. I'm using the SampleWdpClient app and randomly during request to the device, the device responses a request with a 307 state code and the wrapper follows the redirected uri an gets an html page as answer. As result, the deserializer fails because the answer isn't an json string.
In the most of the request, the device answers the request with an 401, the httpclient sends the credentials and all works well. Except in some cases (all 2-4 times) the device answers with an 307 and the wrapper fails.
Do I have to configure the devices differently (I tested more than one with the same result) ?
I'm using the last nuget version (0.9.5.1)
below the wireshark trace:
thanks a million.
The text was updated successfully, but these errors were encountered: