Hi,
I may understand your reply if I was not a developer myself but being such I cannot, especially when saying the problem is somewhere else.
The error is quite clear because I've explained it in the post creation already, I'll report it again below:
~~~PART OF FIRST POST
Debugging bit more found that the problem is due to how the scanner embedded browser is creating a request, below there is a sample header:
POST
http://10.10.10.145:8888/Default.aspx HTTP/1.0
Accept: image/png, image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Host: 10.10.10.145:8888
....
and the problem is in the requested resource, if it is changed to "POST /Default.aspx HTTP/1.0" (so removing full host information) it works perfectly
~~~PART OF FIRST POST
With a sample application I can emulate the bad request and also fix by changing the requested resource. In fact IIS, using the same .NET 4 processor, can serve perfectly the request which means they do something different from Ultidev and which Ultidev can do as well.
Could you please take in consideration the above example? Perhaps .NET 4 is appending the HOST before the resource or something similar very simple making the request bad when the browser will receive such request info, but this can be easily verified by you in debugging by changing the resource as per above while debugging.
Normally this should be fine also in general according HTTP specifications, so perhaps you can find a fix by changing it, when running on .NET 4, if you receive such requests which we know will be considered bad by the framework.
Thanks and Regards,
Luigi Zurolo
