I am running a web server with soop portal on a win2k box and am forced
to use port 800 (due to verizon dsl). Initially when I browse the site
its there but after clicking a link it drops the :8000 added to the
url. Is there a setting in IIS or maybe somewhere in the asp code to
keep the port from changing?
On 25 Apr 2006 17:11:39 -0700, "bmac"
wrote:
>I am running a web server with soop portal on a win2k box and am forced
>to use port 800 (due to verizon dsl). Initially when I browse the site
>its there but after clicking a link it drops the :8000 added to the
>url. Is there a setting in IIS or maybe somewhere in the asp code to
>keep the port from changing?
Nope. It's the link. If the link doesn't include the port it assumes
80.
Jeff
Hi,
Does the link contain :8000? If not, then that is the problem.
Remember that HTTP is a stateless protocol, so the webserver does not
really knows that the client clicked on a link on a page already served by
the server. Once the user clicks the link, the client application connects
to the webserver on the port specified by the link (which will be 80 if
nothing else is specified), hence you cannot use IIS* nor ASP* to control
the connecting behavior of the client, because the client has already
failed to connect (IIS is not aware of that the client is trying to
connect on a port it is not listening on).
* Custom built code (ASP/ISAPI) may be able to rewrite what is sent to the
client and modify the URLs on-the-fly. This is however somewhat
complicated. I would recommend you to use relative paths instead, since
that will overcome this problem (and is recommended for many reasons).
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
bmac wrote:
>I am running a web server with soop portal on a win2k box and am forced
>to use port 800 (due to verizon dsl). Initially when I browse the site
>its there but after clicking a link it drops the :8000 added to the
>url. Is there a setting in IIS or maybe somewhere in the asp code to
>keep the port from changing?
The link does contain :8000. When the site is first visited it appears
fine. However when trying to browse the site, the :8000 gets dropped.
bmac wrote:
> The link does contain :8000. When the site is first visited it appears
> fine. However when trying to browse the site, the :8000 gets dropped.
You must add the port, ':8000', to EVERY internal link within the site.
--
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com
I don't understand. How does :8000 get dropped? Where does this happen?
IIS does not know (nor does it care) if you clicked a link, or typed the
URL manually. So if it works when you type the URL manually (with :8000)
but not when you click the link, there has to be something wrong with the
link.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
bmac wrote:
>The link does contain :8000. When the site is first visited it appears
>fine. However when trying to browse the site, the :8000 gets dropped.
I am referring to the links within the page. I can browse the site fine
on my internal network. It drops the :8000 and assumes 80 (which is
fine internally) however externally when a link is clicked within the
page the :8000 gets dropped. I am using soop web portal, all the asp
pages are already written. I just had to make a couple of config
changes (none of which specify a port to use).
To see if it was the prewritten asp code, I created a couple of asp
pages and the :8000 did not get dropped. I guess to revise my question;
where would be a good starting point to look in the code for a place to
specify or force port 8000 instead of 80?
Bernie Hoffmann
But what/how is :8000 dropped? Can you please right click the link (the
one that has :8000 dropped) and click copy, and then paste it here (you
can replace the server name part if you like, but please keep everything
else)?
Because what you say does not make sense. The client does not drop the
port. IIS does not drop the port. So i cannot understand what you mean by
"it drops the :8000". What is "it"?
To "force" the use of port 8000, all links must use :8000 (i.e. the client
must for each request know that it should use port 8000). HTTP clients are
smart, they do what you tell them to do. If you tell them to connect on
port 80 they do that, if you tell them to connect on port 8000 they do
that. They do not guess, based on earlier requests that one or the other
should be used. They obey your instructions (if you do not specify any
port, according to specifications, port 80 should be used).
So I need to know how your failing link exactly (you can replace the
server name) looks like to be able to tell if the behavior is expected or
wrong.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
bmac wrote:
>I am referring to the links within the page. I can browse the site fine
>on my internal network. It drops the :8000 and assumes 80 (which is
>fine internally) however externally when a link is clicked within the
>page the :8000 gets dropped. I am using soop web portal, all the asp
>pages are already written. I just had to make a couple of config
>changes (none of which specify a port to use).
>
>To see if it was the prewritten asp code, I created a couple of asp
>pages and the :8000 did not get dropped. I guess to revise my question;
>where would be a good starting point to look in the code for a place to
>specify or force port 8000 instead of 80?
>
>Bernie Hoffmann
On 26 Apr 2006 10:53:41 -0700, "bmac"
wrote:
>I am referring to the links within the page. I can browse the site fine
>on my internal network. It drops the :8000 and assumes 80 (which is
>fine internally) however externally when a link is clicked within the
>page the :8000 gets dropped. I am using soop web portal, all the asp
>pages are already written. I just had to make a couple of config
>changes (none of which specify a port to use).
>
>To see if it was the prewritten asp code, I created a couple of asp
>pages and the :8000 did not get dropped. I guess to revise my question;
>where would be a good starting point to look in the code for a place to
>specify or force port 8000 instead of 80?
Review your code. It's not IIS, it's your code.
Jeff