Okay, I've solved it by using the tip provided by Jon00.
As Jon00 is using HttpWebRequest, it should not using the IE settings at all (exept for proxy settings).
I wrote a simple script for testing. It seems that running a script locally gives some different results based on how you've set up permissions. Here's the results. Notice the wrapped web page in the log.
Aha! Yes, the user "data" was set as "Normal+Local" in the Tools -> Setup -> Network page. I set that user to "Normal" (I had another local user aswell), and wouldn't you know:
So, no: It's not ESXi (of course) or any other strange issues. But:
You need to have just one local user, and that user needs to have admin rights (of course).
If you want to test this yourself you can use this script:
As Jon00 is using HttpWebRequest, it should not using the IE settings at all (exept for proxy settings).
I wrote a simple script for testing. It seems that running a script locally gives some different results based on how you've set up permissions. Here's the results. Notice the wrapped web page in the log.
Aha! Yes, the user "data" was set as "Normal+Local" in the Tools -> Setup -> Network page. I set that user to "Normal" (I had another local user aswell), and wouldn't you know:
So, no: It's not ESXi (of course) or any other strange issues. But:
You need to have just one local user, and that user needs to have admin rights (of course).
If you want to test this yourself you can use this script:
Code:
Sub Main(parm As Object) Dim request As System.Net.HttpWebRequest = DirectCast(System.Net.WebRequest.Create("http://localhost/interfaces"), System.Net.HttpWebRequest) Dim response As System.Net.HttpWebResponse = DirectCast(request.GetResponse, System.Net.HttpWebResponse) Dim reader As New System.IO.StreamReader(response.GetResponseStream) Dim output As String = reader.ReadToEnd hs.Writelog("Test interface page", output) End Sub
Comment