-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
On 11/16/2009 2:13 PM, joeweder wrote:
> We have an application where the user comes in through 8443 via https.
>
> But the same app also communicates headlessly with other apps through a
> separate data port (also https).
What port is that? Do
2009/11/16 joeweder :
> Question: How can I disable browser access through a specific port but
> continue to allow headless https through?
You *could* write a Filter that sniffed at the User-Agent header in
the https: request, but most browsers have ways of faking that - you
can't rely on *any* da
challenged (we don't turn on
client-authentication for the data port).
Question: How can I disable browser access through a specific port but
continue to allow headless https through?
--
View this message in context:
http://old.nabble.com/How2-Disable-Browser-Access-to-specific-port-tp26377695p263
