Handling embedded port numbers

[phxazcraig]

In article <4AE56C00.CE15.0032.0@N0_$pam.vrapc.com>, Chris wrote:
> No problem. Hope you had fun camping.

Between strong winds destroying first tent when we tried to put it up,
and invasion of skunks in the evening, it was an adventure of sorts.
>
> I know BM is probably geting close to EOL and OES 2 (Linux)
> does not run BM, but a "rule type" that would allow both
> http and https traffic in one would be really nice.

That is basically what URL rules do. They take care of HTTP traffic
that uses non-standard ports. HTTPS is a special case.
>
> So what you do is essentially create a port 80 rule
> (although it technically is a URL rule) / port 443 rule
> pair?

No. I basically never use a port 80 rule. I use URL rules only, and
then if I need to specifically block or deny some https site that
doesn't want to work with a URL rule, I add a port 443 rule to that
domain. These are exceptions to the normal course of events, and most
of the systems I work on don't have port 443 rules.


Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***