an attempt was made to access a socket in a way forbidden by its access permissions
I discovered that IIS running locally locked up port 80 and that I had to move IIS to another port - you can read how to d os by going to http://www.ultimateproxyli
The problem I still have - even after moving IIS off of Port 80 - is that no listener is actually working. I even grabbed the following code sample directly off the MSDN site and even IT does not work! I am on a Windows 7 machine - any ideas?!?
if (!HttpListener.IsSupported)
{
Console.WriteLine("Windows XP SP2 or Server 2003 is required to use the HttpListener class.");
return;
}
// Create a listener.
HttpListener listener = new HttpListener();
// Add the prefixes.
listener.Prefixes.Add("http://*:80/");
listener.Start();
Console.WriteLine("Listening...");
// Note: The GetContext method blocks while waiting for a request.
HttpListenerContext context = listener.GetContext();
HttpListenerRequest request = context.Request;
// Obtain a response object.
HttpListenerResponse response = context.Response;
// Construct a response.
string responseString = " Hello world!";
byte[] buffer = System.Text.Encoding.UTF8.GetBytes(responseString);
// Get a response stream and write the response to it.
response.ContentLength64 = buffer.Length;
System.IO.Stream output = response.OutputStream;
output.Write(buffer, 0, buffer.Length);
// You must close the output stream.
output.Close();
listener.Stop();
Sam HobbsPosted Mar 8, 2010, 7:25 PM
Ken TolaPosted Mar 8, 2010, 3:59 PM
The issue here is how to listen to traffic as it goes from a browser through a local IP connection and out to the world. None of the listeners or socket classes seem to be able to accomplish this task...
Sam HobbsPosted Mar 8, 2010, 3:55 PM
Do you know what port 80 is used for? I am not sure I understand what you are trying to do, but it makes sense to me that you can't do it. Do you have any browser (such as IE) windows open when you do that? If you can use some other port while testing, then that will probably work better. You can change to port 80 after testing, but my guess is that even then port 80 will be a problem.