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), 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). If I add port :8880 to the URL, Squid redirects correctly to the applicaiton port 8888. Outside:8880 -> squid server -> 8888 same server ----------------------- begin of squid.conf ---------------- #debug_options ALL,1 33,2 debug_options ALL,1 33,2 28,9 # ACL logs -> cache.log log_mime_hdrs on access_log c:/squid/var/logs/access.log cache_log c:/squid/var/logs/cache.log cache_store_log c:/squid/var/logs/store.log cache_peer 127.0.0.1 parent 8888 0 no-query originserver http_port wiki1:8880 accel defaultsite=wiki1 forwarded_for on #visible_hostname wiki1 acl allowed_URL urlpath_regex / #acl allowed_URL urlpath_regex /flexnet/ #acl allowed_URL urlpath_regex /flexnet/logon.do #acl allowed_URL urlpath_regex /flexnet/resources/ #acl allowed_URL urlpath_regex /flexnet/services/ActivationService #acl allowed_URL urlpath_regex /flexnet/services/EntitlementOrderService #acl allowed_URL urlpath_regex /flexnet/services/OrganizationAdministration cache_peer_access 127.0.0.1 allow allowed_URL acl all src 0.0.0.0/0.0.0.0 acl manager proto cache_object acl localhost src 127.0.0.1/255.255.255.255 acl to_localhost dst 127.0.0.0/8 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT http_access allow manager localhost http_access deny manager http_access deny !Safe_ports http_access deny CONNECT !SSL_ports # Example rule allowing access from your local networks. Adapt # to list your IP networks from where browsing should # be allowed #acl our_networks src 192.168.1.0/24 192.168.10.0/24 127.0.0.1/255.255.255.255 acl external_networks src 0.0.0.0/0.0.0.0 acl valid_dst dstdomain wiki1 http_access allow external_networks valid_dst #http_access deny valid_dst http_access deny all icp_access allow all ---------------------- end squid.conf -------------------- On Wed, Apr 9, 2008 at 6:55 PM, Chris Robertson <crobertson@xxxxxxx> wrote: > > Gary Tai wrote: > > > I'm using SquidNT configured as reverse proxy. It works correctly when > > specifying the Squid port in the URL <http://somedomain:8880/someURL>, > > but if the page needs to return another page, the port no longer shows > > up <http://somedomain/some_newURL> and IIS complains that no page > > exists. If I explicitly put in the port > > <http://somedomain:8880/some_newURL>, the reverse proxy returns the > > correct page. > > > > This used to work but stopped at some time. > > > > Any help appreciated. > > > > Thanks, > > > > Gary > > > > > > What version of Squid? What does your squid.conf (without comments > preferably) look like? > > From the limited information given, it sounds like Squid and IIS are > running on the same machine (Squid on port 8080, IIS on port 80) and the IIS > listening on port 80 doesn't have the same information as Squid's origin > server. If this is the case, getting IIS off port 80 (and letting Squid > listen in its stead) likely should solve the problem. > > Chris >
