Right, and that was my initial approach, but it seemed to have the
effect of blocking traffic to port 80.
As I've said, I'm not seeing it as a real problem, but rather just
letting people know that it is an ugliness associated with this (NAT)
approach.
On Sat, 2007-04-07 at 12:26 -0400, Mark
On Apr 7, 2007, at 12:08 PM, Mark H. Wood wrote:
On Fri, Apr 06, 2007 at 12:07:44PM -0400, Cory Snavely wrote:
For folks listening in with interest, we also use NAT port
forwarding to
get around the requirement for mod_jk, but FWIW I haven't
determined a
way to close the incoming
We use Apache, mod_jk and mod_rewrite to deliver the webapplication
on port 80 and port 443 as separate VirtualHost entries in Apache
httpd. We do not allow direct access to the tomcat server over port
8080 or port 8443. I can send some more detail of our configuration
if you decide to go
For folks listening in with interest, we also use NAT port forwarding to
get around the requirement for mod_jk, but FWIW I haven't determined a
way to close the incoming *actual* Tomcat ports (8080/8443). So, a
potential downside with this approach, in addition to not having any
real logic like
, April 06, 2007 10:08 AM
To: dspace-tech@lists.sourceforge.net
Cc: Zhiwu Xie
Subject: Re: [Dspace-tech] redirect port 8443 to 80?
For folks listening in with interest, we also use NAT port forwarding to
get around the requirement for mod_jk, but FWIW I haven't determined a
way to close the incoming
Hello,
I'm following the Dspace wiki page DspaceOnStandardPorts and
ServletSecurity to run Dspace on Tomcat only. I've set up iptables to
route port 80 to 8080 and 443 to 8443, then set the Tomcat
redirectPort to 443 instead of 8443, so I don't get the 8443 port
number such as
6 matches
Mail list logo
