HttpStatusCode 307 handling about windowsdeviceportalwrapper HOT 4 OPEN

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.

from windowsdeviceportalwrapper.

Hello @hpsin thanks a lot for the explanation. Yes, I'm using Win10 IoT on a raspberry.

I fixed it quick & dirty in GetAsync<..> by executing the request again in case the response status code is 307.

That helps as long no other clients request the page parallel as implemented in the WDP.

from windowsdeviceportalwrapper.

Thanks! That's a good workaround. I'm going to leave this open until @namkedia confirms that the fix internally is checked in.

from windowsdeviceportalwrapper.

Push for fix in trunk.

from windowsdeviceportalwrapper.