Hi there,
I´d like to allow users to enter a website which is on port 100, with having
to specify the port number. Eg, instead of http://sharepoint:100, redirect
the traffic to http://sharepoint (or another name.)
Is this achievable through IIS?
Thanks in advance.
Hi,
I don't know if there is a word missing in your message, or if i don't
understand.
Do you want people to access the website using http://sharepoint/ but this
website is running on port 100 and not 80? If so, that is not possible to
do. You must have something listening on port 80, because the client will
establish a connection on port 80.
Talking about redirections, what kind of redirection are you looking for? I
have a feeling that you do not want a redirect as in http redirect (status
code 30X) because it would not make much sense to give out a URL specifying
port 100 when you, on the same machine, run a website on port 80 that you
want to use. Why not use port 80 directly?
Do you want a server-side redirection (transparent to the user, they think
they connect on port 80 but the server is forwarding the request to a
webserver running on port 100)?
I think some important information is missing for me to be able to give a
good solution for you.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
"johnny_mango"
news:DBD53F42-6BCA-486C-82E5-C564F45764BD@microsoft.com...
> Hi there,
>
> I´d like to allow users to enter a website which is on port 100, with
> having
> to specify the port number. Eg, instead of http://sharepoint:100, redirect
> the traffic to http://sharepoint (or another name.)
>
> Is this achievable through IIS?
>
> Thanks in advance.
Thanks a lot for your response.
Scenarios 1 and 3 of your analysis are the kinds of things I´d like to do.
It isn´t too clear to me the difference between the two, but either solution,
providing we have the infrastructure, would be grand.
To confirm, the client would use http://sharepoint to connect to a website
which runs on port 100 with another server name. The redirectioning of server
names should be straightforward with DNS, but the port requirement?
Thanks again.
"Kristofer Gafvert" wrote:
> Hi,
>
> I don't know if there is a word missing in your message, or if i don't
> understand.
>
> Do you want people to access the website using http://sharepoint/ but this
> website is running on port 100 and not 80? If so, that is not possible to
> do. You must have something listening on port 80, because the client will
> establish a connection on port 80.
>
> Talking about redirections, what kind of redirection are you looking for? I
> have a feeling that you do not want a redirect as in http redirect (status
> code 30X) because it would not make much sense to give out a URL specifying
> port 100 when you, on the same machine, run a website on port 80 that you
> want to use. Why not use port 80 directly?
>
> Do you want a server-side redirection (transparent to the user, they think
> they connect on port 80 but the server is forwarding the request to a
> webserver running on port 100)?
>
> I think some important information is missing for me to be able to give a
> good solution for you.
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> "johnny_mango"
> news:DBD53F42-6BCA-486C-82E5-C564F45764BD@microsoft.com...
> > Hi there,
> >
> > I´d like to allow users to enter a website which is on port 100, with
> > having
> > to specify the port number. Eg, instead of http://sharepoint:100, redirect
> > the traffic to http://sharepoint (or another name.)
> >
> > Is this achievable through IIS?
> >
> > Thanks in advance.
>
>
johnny_mango wrote on Tue, 27 Nov 2007 21:50:01 -0800:
> Thanks a lot for your response.
> Scenarios 1 and 3 of your analysis are the kinds of things I´d like to
> do.
> It isn´t too clear to me the difference between the two, but either
> solution, providing we have the infrastructure, would be grand.
> To confirm, the client would use http://sharepoint to connect to a
> website which runs on port 100 with another server name. The
> redirectioning of server names should be straightforward with DNS, but
> the port requirement?
> Thanks again.
If you want the client to always see http://sharepoint in the address bar,
then a couple of options are: have to have a web server on port 80 on the IP
mapped to the sharepoint host which then generates a HTML frameset, and has
a frame refering to http://otherserver:100 ; a HTTP proxy server running on
that port 80 to act as a gateway between the users and the actual server.
If you just want the initial port 80 connection to redirect to the real
host, so the URL acts as a "shortcut", then you just need a web server
running on port 80 on sharepoint that sends a HTTP location response to the
client to give it the name and port of the server to redirect to.
Dan