jevakallio
jevakallio

Reputation: 35960

Monitoring traffic to Cassini on localhost

I'm experiencing some really odd timeout issues when running a ASP.NET 2.0 project on Cassini on localhost, and I don't have enough data to get a clue of what's going on.

Is there a way to monitor localhost traffic to Cassini, either using some specific development tool or a general-purpose monitoring app such as fiddler?

Just to pre-empt some answers I'm already aware of:

Any other tools or fiddler workarounds welcome! Thanks!

Edit: Oops. This question had already been asked... Twice.. Didn't come up on search or suggestions. The solution found in the second thread is to use the dot-hack with ip-address (http://127.0.0.1.:port/ instead of "localhost". This question may be closed.

Upvotes: 0

Views: 1070

Answers (3)

Sky Sanders
Sky Sanders

Reputation: 37104

CassiniDev is an open source project that was developed to fill in all the blanks left by WebDev.WebServer/Cassini.

You will find this issue handled as well as many others.

It works well as a stand-alone server, as an in-process server suitable for testing and embedding and, most notably, as a direct replacement for the Visual Studio 2008/2010 dev servers.

alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=cassinidev&DownloadId=123367

alt text http://i3.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=cassinidev&DownloadId=123366

Upvotes: 0

EricLaw
EricLaw

Reputation: 57115

You're generally better off using http://ipv4.fiddler as it makes it more explicit what you're trying to do.

Upvotes: 0

jevakallio
jevakallio

Reputation: 35960

While fiddler ignores requests to localhost, it listens to 127.0.0.1. (note the trailing dot):

So this won't work:

http://localhost:1234/

But this will:

http://127.0.0.1.:1234/

Upvotes: 1

Related Questions