Why can't I profile a site with a different port than 80?
Comments
5 comments
-
Hi Ollie,
Originally the reason that ANTS Profiler needs the website to run on port 80 was to work around a problem with IIS in determining if the website is running again after a profiling session had finished.
This is a planned fix for version 2. Rather than checking port 80, we'll parse the port number from the URL of the web application that you are profiling to determine what TCP port to check. -
It will be out in 3-4 weeks. We've already released a private Beta version for testing so it's nearly complete.
-
Any chance I can get a copy of the beta at all?
It might convince me to buy a license -
We haven't put the bits in the Beta yet to allow it to profile different ports.
-
ANTS Profiler 2.5 now supports this as well as profiling websites using different host headers.
Add comment
Please sign in to leave a comment.