IIS and Host Names

All
I've got an IBM M/F calling, via CICS web support, an IIS 6.0 installation.
For various reasons I'm being asked to host the web server on port 82 which
I've done. When our m/f calls a web server on any port other than 80 it
adds the port number to the host name with the port number being 0 filled to
5 characters so the host name parameter is like my-server:00082.

This appears to cause IIS an issuse and IIS returns an http 400 Invalid
Request (Bad Hostname). From my MS platform I can set mimic this problem by
settig the hostname to that which the m/f sets and equallt I can solve the
prblem by dropping the 0s so my-server:82 works. Unfortunately we don;t
appear to have the ability to drop the 0s from the m/f request and I've
tried to use the headers to redirect to port 80 but I'm not able to enter
either 00082 or my-server:00082 and I'm now out of ideas.

Anyone seen this before and can suggest a way forward?

Cheers

--
My Inbox is a temple - please remove SHOES before entering

AP

_
Mon Jun 25 09:02:36 CDT 2007

Can the mainframe call on port 80? The solution and avoidance of all this
could be easy, just get another IP on your network interface and run on port
80. (assuming something else is on port 80)

Using port 82 is a sign you are trying to get around some security or
network restriction, you are best off working with the person responsible
rather than trying to circomvent what they are doing, as they could easily
dectect your traffic and cut you off when it is least convenient for you.

"Wor Tony" <anthony@SHOESanthonypounder.com> wrote in message
news:U4Bfi.4348$nE2.2331@newsfe3-win.ntli.net...
> All
> I've got an IBM M/F calling, via CICS web support, an IIS 6.0
> installation. For various reasons I'm being asked to host the web server
> on port 82 which I've done. When our m/f calls a web server on any port
> other than 80 it adds the port number to the host name with the port
> number being 0 filled to 5 characters so the host name parameter is like
> my-server:00082.
>
> This appears to cause IIS an issuse and IIS returns an http 400 Invalid
> Request (Bad Hostname). From my MS platform I can set mimic this problem
> by settig the hostname to that which the m/f sets and equallt I can solve
> the prblem by dropping the 0s so my-server:82 works. Unfortunately we
> don;t appear to have the ability to drop the 0s from the m/f request and
> I've tried to use the headers to redirect to port 80 but I'm not able to
> enter either 00082 or my-server:00082 and I'm now out of ideas.
>
> Anyone seen this before and can suggest a way forward?
>
> Cheers
>
> --
> My Inbox is a temple - please remove SHOES before entering
>
> AP
>

Andrew
Thu Jun 28 05:39:58 CDT 2007

Wor Tony wrote:
> I've got an IBM M/F calling, via CICS web support, an IIS 6.0
> installation. For various reasons I'm being asked to host the web
> server on port 82 which I've done. When our m/f calls a web server
> on any port other than 80 it adds the port number to the host name
> with the port number being 0 filled to 5 characters so the host name
> parameter is like my-server:00082.
> This appears to cause IIS an issuse and IIS returns an http 400
> Invalid Request (Bad Hostname). From my MS platform I can set mimic
> this problem by settig the hostname to that which the m/f sets and
> equallt I can solve the prblem by dropping the 0s so my-server:82
> works. Unfortunately we don;t appear to have the ability to drop the
> 0s from the m/f request and I've tried to use the headers to redirect
> to port 80 but I'm not able to enter either 00082 or my-server:00082
> and I'm now out of ideas.
> Anyone seen this before and can suggest a way forward?

Maybe, just maybe, the zero-padding makes IIS see it as an octal number, in
the way IP addresses are assumed to be octal if they are in the form
001.002.003.004, so you could try telling the m/f to use port "122".

Andrew

Wor
Sat Jun 30 10:55:54 CDT 2007

The m/f can call on port 80 only at the dev platform level. Above that
platform, internal firewalls prevent this traffic on port 80 but do allow it
on port 82 (I don't know why this is). We can open the internal firewalls
but policys and procedures make this a 3 month wait and we can't afford to
wait for this.

In the meantime we have come to a temporary solution (cringes); some ports
above 9999 are open and we have found that we can utilise one of these 5
digit ports and have IIS listen on them without a problem. We will open
them and switch back to port 80 when the firewall changes are in place.

Thanks for your input.

--
My Inbox is a temple - please remove SHOES before entering

AP
".._.." <.._..@yourmom.mil> wrote in message
news:0WPfi.35840$G23.7023@newsreading01.news.tds.net...
> Can the mainframe call on port 80? The solution and avoidance of all this
> could be easy, just get another IP on your network interface and run on
> port 80. (assuming something else is on port 80)
>
> Using port 82 is a sign you are trying to get around some security or
> network restriction, you are best off working with the person responsible
> rather than trying to circomvent w