The web application works correctly without Squid. It returns the correct page with the port number. It's only when Squid is used to intercept that the port is dropped. On Thu, Apr 10, 2008 at 4:32 PM, Chris Robertson <crobertson@xxxxxxx> wrote: > Gary Tai wrote: > > > Sorry for being vague. You are correct, squid is on the same server as > > the application listening on port 8888. I can access the login page > > correctly through Squid port 8880 (which redirects to port 8888) > > > > For clarity, this redirection is termed proxying > (http://en.wikipedia.org/wiki/Reverse_proxy). Redirection refers to another > action in this context > (http://en.wikipedia.org/wiki/URL_redirection#HTTP_status_codes_3xx). > > > > > , when > > I click on the "Login" button, the next page doesn't have port 8880 in > > the URL, in fact, it has no port at all specified so it defaults to 80 > > (which IIS has no files for). > > > > Right. Well, either you need to get the login page to redirect (as in an > HTTP 301 or 302 redirect) to port 8080, or you need to get Squid listening > on port 80. > > Chris >
