standing is that TRACE got its poor reputation due to a
> >>> misbehaving browser. Rather than pressure the browser vendor to fix
> >>> their broken browser, the security community decided to pressure the
> >>> server community to disable the functionality th
Thanks,
Bhavesh
On Fri, Oct 7, 2022 at 10:59 AM Mark Thomas wrote:
On 07/10/2022 18:09, Bhavesh Mistry wrote:
Hi Tomcat Team,
We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP
method
on port 80 and 443.
We have connector definitions as follows:
have been at the time and how reluctant to
>> change the vendor was.
>>
>> CONNECT returns 405 by default in a Servlet container and none of TRACE,
>> OPTIONS or HEAD are inherently unsafe.
>>
>> Mark
>>
>>
>> >
>
gt; Mark
>
>
> >
> > Thanks,
> >
> > Bhavesh
> >
> > On Fri, Oct 7, 2022 at 10:59 AM Mark Thomas wrote:
> >
> >> On 07/10/2022 18:09, Bhavesh Mistry wrote:
> >>> Hi Tomcat Team,
> >>&g
n a Servlet container and none of TRACE,
OPTIONS or HEAD are inherently unsafe.
Mark
Thanks,
Bhavesh
On Fri, Oct 7, 2022 at 10:59 AM Mark Thomas wrote:
On 07/10/2022 18:09, Bhavesh Mistry wrote:
Hi Tomcat Team,
We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP
m
> We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP
> method
> > on port 80 and 443.
> >
> > We have connector definitions as follows:
> >
> >
> > > port="8080" protocol="HTTP/1.1"
&
On 07/10/2022 18:09, Bhavesh Mistry wrote:
Hi Tomcat Team,
We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP method
on port 80 and 443.
We have connector definitions as follows:
-->
-->
and we have an application filter to blo
Hi Tomcat Team,
We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP method
on port 80 and 443.
We have connector definitions as follows:
-->
-->
and we have an application filter to block and return 405. This works for
HTTPS port 443
> Mark
>
>
> >
> > Thank you
> >
> > On Sun, Jul 10, 2022 at 4:49 AM Mark Thomas wrote:
> >
> >> On 10/07/2022 05:40, Jason Zhang wrote:
> >>> Hello Tomcat Support team,
> >>>
> >>> The Tomcat is not responding to
t how Alfresco works or the root
cause of the problem you are seeing, anything is possible.
Mark
Thank you
On Sun, Jul 10, 2022 at 4:49 AM Mark Thomas wrote:
On 10/07/2022 05:40, Jason Zhang wrote:
Hello Tomcat Support team,
The Tomcat is not responding to requests to port 80 in our sy
> On 10/07/2022 05:40, Jason Zhang wrote:
> > Hello Tomcat Support team,
> >
> > The Tomcat is not responding to requests to port 80 in our system, I
> would
> > like to know:
> > 1. If this is an issue with Tomcat or outside the Tomcat
> > 2. If it is an issu
On 10/07/2022 05:40, Jason Zhang wrote:
Hello Tomcat Support team,
The Tomcat is not responding to requests to port 80 in our system, I would
like to know:
1. If this is an issue with Tomcat or outside the Tomcat
2. If it is an issue with Tomcat, how to fix it
3. If it is outside the Tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jerry,
On 7/18/20 18:29, Jerry Malcolm wrote:
> I'm taking Christopher's advice to remove httpd and mod_jk out of
> my process and go straight to Tomcat on port 80. At this point the
> only thing I've done is stop the http
I'm taking Christopher's advice to remove httpd and mod_jk out of my
process and go straight to Tomcat on port 80. At this point the only
thing I've done is stop the httpd service and change the Connector port
to 80. I'm running on my local machine. I have
e allowed.
Requirements are requirements, but this one is a bad idea.
https://scotthelme.co.uk/why-closing-port-80-is-bad-for-security/
> I have implemented SSL and the same is working fine. however,
> still, tomcat is showing listening on 80. so can we disable
> (comment ) port 80 connector fro
>> -Original Message-
>> From: Nitin Kadam
>> Sent: Wednesday, January 29, 2020 9:50 AM
>> To: Tomcat Users List >>
>> Subject: Tomcat 8.5 disabling port 80 listening
>> Hi Team,
>> I have a tomcat 8.5 server configured in the production
80. so can we disable (comment ) port 80 connector
from server.xml which will only allow access to the portal with Https.
>From :
To :
--
Regards
Nitin Kadam
pache Tomcat 9.0.21
binary installation. I compiled the JSVC and created a setenv.sh file with some
environmental variables. Tested starting Tomcat with daemon.sh and it came up
on 8080. Now to get it to work on port 80:
Install authbind and configure it
o sudo apt install authbind
o
with daemon.sh and it came up
on 8080. Now to get it to work on port 80:
Install authbind and configure it
o sudo apt install authbind
o sudo touch /etc/authbind/byport/80
o sudo chmod 500 /etc/authbind/byport/80
o sudo chown tomcat /etc/authbind/byport/80 (this assumes y
t seems that the issue below is more of a question for the
>> Ubuntu list, than Tomcat's.
>>
>> The standard /etc/init.d/tomcat9 startup script included in the
>> Ubuntu tomcat9 package, should allow starting tomcat 9 on port 80
>> without any changes to the tomcat
list,
than Tomcat's.
The standard /etc/init.d/tomcat9 startup script included in the Ubuntu
tomcat9 package,
should allow starting tomcat 9 on port 80 without any changes to the
tomcat configuration
or scripts (other than setting the Connector to port 80 in server.xml).
that the issue below is more of a question for the Ubuntu list,
than Tomcat's.
The standard /etc/init.d/tomcat9 startup script included in the Ubuntu
tomcat9 package,
should allow starting tomcat 9 on port 80 without any changes to the tomcat
configuration
or script
Hi.
Apologies for breaking conventions of this list and top-posting..
It seems that the issue below is more of a question for the Ubuntu list, than
Tomcat's.
The standard /etc/init.d/tomcat9 startup script included in the Ubuntu tomcat9 package,
should allow starting tomcat 9 on po
Hello,
I have Tomcat 9.0.21 installed (binary distribution) on an Ubuntu 16.04 server.
My Java version is OpenJDK 11.0.4. I have the JSVC built and run the dameon.sh
script to start and stop Tomcat via a systemd script. Everything works great,
but now I need to run it on port 80 & 443. On
2015-11-04 20:20 GMT+03:00 Linux Support :
> Hi again,
>
> configured the TC service to run as a non privileged user. In my
> understanding we cannot use a privileged port to bind TC to. Is there a way
> i can use port 80 for TC in the case of using a non root user ?
http://to
leged port to bind TC to. Is there a way
i can use port 80 for TC in the case of using a non root user ?
cheers
osp
--
George Sexton
*MH Software, Inc.*
Voice: 303 438 9585
http://www.mhsoftware.com
Hi again,
configured the TC service to run as a non privileged user. In my
understanding we cannot use a privileged port to bind TC to. Is there a way
i can use port 80 for TC in the case of using a non root user ?
cheers
osp
rom: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Wednesday, October 28, 2015 3:31 PM
To: Tomcat Users List
Subject: Re: Tomcat answers on port 80, not on 443
Gregory,
On 10/27/15 1:57 PM, Beyer, Gregory L wrote:
> Still struggling with this. I'm amazed that implementing SSL in
> Tomcat
Gregory,
On 10/27/15 1:57 PM, Beyer, Gregory L wrote:
> Still struggling with this. I'm amazed that implementing SSL in
> Tomcat is so difficult. It's not in straight Apache, or IIS. Is
> Tomcat really so different an animal?
No, Tomcat is not so different an animal. But you aren't using Tomc
ssage-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Saturday, October 24, 2015 8:06 AM
To: Tomcat Users List
Subject: Re: Tomcat answers on port 80, not on 443
André,
On 10/23/15 4:16 PM, André Warnier (tomcat) wrote:
> On 23.10.2015 16:53, Beye
André,
On 10/23/15 4:16 PM, André Warnier (tomcat) wrote:
> On 23.10.2015 16:53, Beyer, Gregory L wrote:
> ...
> ##
> # Inbound SSL Settings
> ##
>
> org.apache.felix.https.enable=true
> org.osgi.service.http.port.sec
On 23.10.2015 16:53, Beyer, Gregory L wrote:
...
##
# Inbound SSL Settings
##
org.apache.felix.https.enable=true
org.osgi.service.http.port.secure=443
org.apache.felix.https.keystore=E:\\Progra
olinko [mailto:knst.koli...@gmail.com]
Sent: Friday, October 16, 2015 10:54 PM
To: Tomcat Users List
Subject: Re: Tomcat answers on port 80, not on 443
2015-10-15 20:48 GMT+03:00 Beyer, Gregory L :
>
> Hello,
>
> I'm trying to get my web app, which is otherwise running fine on por
Gregory,
On 10/15/15 1:48 PM, Beyer, Gregory L wrote:
> ##
> # Inbound SSL Settings
> ##
>
> org.apache.felix.https.enable=true
> org.osgi.service.http.port.secure=443
> org.apache.felix.https.keystore=E:\keystore\scilexcon
> #org.apache.fel
2015-10-15 20:48 GMT+03:00 Beyer, Gregory L :
>
> Hello,
>
> I'm trying to get my web app, which is otherwise running fine on port 80 to
> respond on SSL. Sorry if this is a resend. I only just started getting
> list messages so my first may not have gone. Don't
Hello,
I'm trying to get my web app, which is otherwise running fine on port 80 to
respond on SSL. Sorry if this is a resend. I only just started getting list
messages so my first may not have gone. Don't intend to bump.
Scenario:
The server in question is a Windows12 web a
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, June 24, 2014 2:42 PM
To: Tomcat Users List
Subject: Re: Browsers suddenly start timing out when accessing port 80 of
secure site
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruce,
On 6/23/14, 2:30 PM, Bruce Lombardi
hristopher Schultz [mailto:ch...@christopherschultz.net]
>> Sent: Tuesday, June 24, 2014 2:42 PM
>> To: Tomcat Users List
>> Subject: Re: Browsers suddenly start timing out when accessing port 80 of
>> secure site
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash:
Hi,
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Tuesday, June 24, 2014 2:42 PM
> To: Tomcat Users List
> Subject: Re: Browsers suddenly start timing out when accessing port 80 of
> secure site
>
> -
2014
>>> 11:33 AM To: users@tomcat.apache.org Subject: Browsers suddenly
>>> start timing out when accessing port 80 of secure site
>>>
>>> We have a Java application running on Tomcat 7.0.52 on an
>>> Amazon Web Services EC2 Windows 2008 R2 server. Tomca
e might be
problems with 8443.
- Bruce
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, June 20, 2014 10:51 AM
To: Tomcat Users List
Subject: Re: Browsers suddenly start timing out when accessing port 80 of
secure site
-BEGIN PGP SIGN
ly start
>> timing out when accessing port 80 of secure site
>>
>> We have a Java application running on Tomcat 7.0.52 on an Amazon
>> Web Services EC2 Windows 2008 R2 server. Tomcat is setup so that
>> our application is the root application and is accessible
> -Original Message-
> From: Bruce Lombardi [mailto:brlom...@gmail.com]
> Sent: Thursday, June 19, 2014 11:33 AM
> To: users@tomcat.apache.org
> Subject: Browsers suddenly start timing out when accessing port 80 of
> secure site
>
> We have a Java application run
We have a Java application running on Tomcat 7.0.52 on an Amazon Web
Services EC2 Windows 2008 R2 server. Tomcat is setup so that our application
is the root application and is accessible from port 80. The application and
Tomcat are configured with SSL so that whenever anyone types in the url for
Peter wrote:
I am happy that you guys sent reply to me, but anyone here can create
configuration file for me for example which I had mentioned in beginning of
post, then I can understand better, its my weakness but true.
Peter, you should decide what you want, and whether the way in which to d
On 12/28/2013 11:00 PM, Peter wrote:
I am happy that you guys sent reply to me, but anyone here can create
configuration file for me for example which I had mentioned in beginning of
post, then I can understand better, its my weakness but true.
-Peter
On Sat, Dec 28, 2013 at 10:25 PM, André War
I am happy that you guys sent reply to me, but anyone here can create
configuration file for me for example which I had mentioned in beginning of
post, then I can understand better, its my weakness but true.
-Peter
On Sat, Dec 28, 2013 at 10:25 PM, André Warnier wrote:
> Peter wrote:
> ...
>
>
Peter wrote:
...
I am confused about installation part please help me, installation guide
says its WEB-INF directory which WEB-INF ?? and I didn't find any lib
directory look at the following detail, I am newbie I have lot of need of
you people's help please do the needful.
Maybe you could s
tomcat uses port 80, so by default when I enter any of above hostname on
browser I could see default index page, but my interest is like below
if I enter *http://client1.host.com <http://client1.host.com>* on browser,
then tomcat should forward it to webapp client1
*http://client1.host.com/c
On Sat, Dec 28, 2013 at 6:48 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> From: Peter [mailto:nex@gmail.com]
> Subject: tomcat - How to forward request to some webapp while using port
80 without virtual host, without apache
> if I enter *http://client1
> From: Peter [mailto:nex@gmail.com]
> Subject: tomcat - How to forward request to some webapp while using port 80
> without virtual host, without apache
> if I enter *http://client1.host.com <http://client1.host.com>* on browser,
> then tomcat should forward it to we
Hi all, I have many entries in /etc/hosts file, like this
cat /etc/hosts
127.0.0.1 main.host.com localhost
::1localhost6.localdomain6 localhost6
a.b.c.d client1.host.com hostname
a.b.c.d client1.host.com hostname
in webapp directory, webapp folders
client1
client2
my tomcat uses port
André,
On 15.5.2013 23:56, André Warnier wrote:
Anyway, to get back to the OP's original issue, and considering the
documentation only, I do understand a bit of confusion as to what is
really being logged in the Access Log.
Yes, I see. You are right, the documentation or the behavioir of
para
Chris,
On 15.5.2013 16:47, Christopher Schultz wrote:
I see that only the URI is being send in the first-line of the
request, and not the protocol-qualified URL. Ognjen asserted that most
user agents send the whole URL but I have not observed this -- neither
today nor in the past. I think most b
the port the server is listening on
getServerPort() returns the port in the HTTP request but this is
overridden by the setting of proxyPort
> Suppose one has one Tomcat, with the HTTP Connector configured to listen
> on port 8080.
> And suppose that one has 2 proxies (with different
e HTTP Connector configured to listen on
port 8080.
And suppose that one has 2 proxies (with different names) each listening on port 80 and
forwarding requests to that one Tomcat on port 8080.
There would then be no possibility to configure Tomcat so as to respond correctly to both
proxies, no ?
(Whi
On 15/05/2013 17:15, André Warnier wrote:
> Ognjen Blagojevic wrote:
>> André,
>>
>> On 15.5.2013 15:38, André Warnier wrote:
>>> As far as I understand here, we are not talking about a proxy situation,
>>> we are talking about Iptables, which does not proxy, it just modifies
>>> packets.
>>> So th
figuration. If the client uses HTTP 1.1, where
host header is mandatory, Tomcat will read host header. If there is a
port specified in the value of the host header it will be read. If there
is no port specified in the host header that Tomcat will assume port 80
for HTTP and port 443 for HTTPS.
Ye
ts
>>>> all packets received on port 8080 to port 80. It will not
>>>> alter the contents of the packets. Therefore, Tomcat will
>>>> receive your HTTP request as it is sent by your browser --
>>>> which means it will contain port 8080 and not port 80. T
1.1, where
host header is mandatory, Tomcat will read host header. If there is a
port specified in the value of the host header it will be read. If there
is no port specified in the host header that Tomcat will assume port 80
for HTTP and port 443 for HTTPS.
Or is there just something not
Mark Thomas wrote:
On 15/05/2013 14:16, André Warnier wrote:
Ognjen Blagojevic wrote:
Iptables will not change the URL. Iptables merely redirects all
packets received on port 8080 to port 80. It will not alter the
contents of the packets. Therefore, Tomcat will receive your HTTP
request as
On 15/05/2013 14:16, André Warnier wrote:
> Ognjen Blagojevic wrote:
>> Iptables will not change the URL. Iptables merely redirects all
>> packets received on port 8080 to port 80. It will not alter the
>> contents of the packets. Therefore, Tomcat will receive your HTTP
>
will
redirect the request coming at port 8080 to port 80, and request
coming at port 8443 to 443.
-A PREROUTING -p tcp -m tcp --dport 8443 -j REDIRECT --to-ports 443
-A PREROUTING -p tcp -m tcp --dport 8080 -j REDIRECT --to-ports 80
Your configuration is a bit unusual. You have Tomcat running
request coming at port 8080 to port 80, and request coming at port 8443 to
443.
-A PREROUTING -p tcp -m tcp --dport 8443 -j REDIRECT --to-ports 443
-A PREROUTING -p tcp -m tcp --dport 8080 -j REDIRECT --to-ports 80
Your configuration is a bit unusual. You have Tomcat running on port 80,
but you add
On 6 Feb 2013 14:06, "Caldarale, Charles R"
wrote:
>
> > From: Brett Delle Grazie [mailto:brett.dellegra...@gmail.com]
> > Subject: Re: Tomcat in port 80 and Debian
>
> > > This topic is mentioned in the FAQ,
> > >
http://wiki.apache.org/tomcat/HowT
.x86_64 : Java daemon launcher
I think using jsvc is a much better route to take if you're running
Tomcat on port 80.
. . . . just my two cents.
/mde/
Following up on my own post:
I'd download the tomcat-jsvc.noarch and unpack it to see what they did.
Then I'd get the Apache Commo
using jsvc is a much better route to take if you're running
Tomcat on port 80.
. . . . just my two cents.
/mde/
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
2013/2/6 Karolis Monkus :
> Ok guys, i did what you all said:
> Removed that crappy 3rd party tomcat and downloaded tomcat tarball and port
> changing works fine. Now i need to run tomcat as service and since it's a
> Fedora it uses systemd instead init. So i created file called tomcat.service
> an
> From: Brett Delle Grazie [mailto:brett.dellegra...@gmail.com]
> Subject: Re: Tomcat in port 80 and Debian
> > This topic is mentioned in the FAQ,
> > http://wiki.apache.org/tomcat/HowTo#How_to_run_Tomcat_without_root_privileges.3F
> Another alternative to those in the F
"service tomcat start"
Am i missing some more information in that tomcat.service file?
Thanks,
Karolis M.
- Original Message -
From: "Caldarale, Charles R"
To: "Tomcat Users List"
Sent: Tuesday, February 05, 2013 5:15 PM
Subject: RE: can'
On 5 Feb 2013 10:58, "Konstantin Kolinko" wrote:
>
> 2013/2/5 Roberto :
> > Hi,
> >
> > I need help with a seemingly trivial question: How to make tomcat use
> > port 80.
> >
> > I have fresh Debian 6.0.6/64 bit install, with Tomcat 6 install
From: "Caldarale, Charles R"
To: Tomcat Users List
Sent: Tuesday, 5 February 2013 8:15 PM
Subject: RE: can't start tomcat on port 80
> From: Karolis Monkus [mailto:karolis.mon...@dts-solutions.lt]
> Subject: can't start tomcat on port 80
>
On 2/5/2013 8:04 AM, Jukka Ruohonen wrote:
On Tue, Feb 05, 2013 at 04:37:42PM +0200, Karolis Monkus wrote:
I use fedora 17 and from yum downloaded tomcat-7.0.33 version. I changed
port from 8080 to 80 in server.xml, restarted tomcat and got the following
error in catalina.out file:
How are you
On Tue, Feb 05, 2013 at 04:37:42PM +0200, Karolis Monkus wrote:
> I use fedora 17 and from yum downloaded tomcat-7.0.33 version. I changed
> port from 8080 to 80 in server.xml, restarted tomcat and got the following
> error in catalina.out file:
How are you (re)starting Tomcat?
As far as I know,
> From: Karolis Monkus [mailto:karolis.mon...@dts-solutions.lt]
> Subject: Re: can't start tomcat on port 80
> Nothing running on 80 port, selinux and firewall disabled, so no
> need for writing iptables rules.
Good to kno.w
> What do you mean by saying i need support from
/run it?
Regards,
Karolis M.
- Original Message -
From: "Caldarale, Charles R"
To: "Tomcat Users List"
Sent: Tuesday, February 05, 2013 4:45 PM
Subject: RE: can't start tomcat on port 80
From: Karolis Monkus [mailto:karolis.mon...@dts-solutions.lt]
Subject: c
> From: Karolis Monkus [mailto:karolis.mon...@dts-solutions.lt]
> Subject: can't start tomcat on port 80
> I use fedora 17 and from yum downloaded tomcat-7.0.33 version.
You may need support from Fedora, since repackaged versions of Tomcat do not
always behave the way real
Hi everyone,
I use fedora 17 and from yum downloaded tomcat-7.0.33 version. I changed port
from 8080 to 80 in server.xml, restarted tomcat and got the following error in
catalina.out file:
SEVERE: Failed to initialize end point associated with ProtocolHandler
["http-bio-80"]
java.net.BindExce
2013/2/5 Roberto :
> Hi,
>
> I need help with a seemingly trivial question: How to make tomcat use
> port 80.
>
> I have fresh Debian 6.0.6/64 bit install, with Tomcat 6 installed.
> Following some messages, I found in Debian a setting in
> /etc/default/tomcat that would so
Hi,
I need help with a seemingly trivial question: How to make tomcat use
port 80.
I have fresh Debian 6.0.6/64 bit install, with Tomcat 6 installed.
Following some messages, I found in Debian a setting in
/etc/default/tomcat that would solve my problem, which is setting
AUTHBIND=yes. The
On Tue, Feb 07, 2012 at 12:06:12PM -0600, Ole Ersoy wrote:
> Thanks Andre and John. I used jsvc to run tomcat before. Maybe
> that's what got me around the root user restriction.
That is exactly what it is for, and I can't imagine why every distro
doesn't use it instead of the arcane scripting t
- Original Message -
> From: Ole Ersoy
> To: Tomcat Users List
> Cc:
> Sent: Tuesday, February 7, 2012 10:06 AM
> Subject: Re: Running Tomcat on Port 80 with Fedora 16 without IP tables
> redirect
>
>T hanks Andre and John. I used jsvc to run tomcat before.
entry/install_tomcat_7_on_centos
Cheers,
- Ole
On 02/07/2012 11:38 AM, John Renne wrote:
On Feb 7, 2012, at 6:14 PM, Ole Ersoy wrote:
Hi,
In the past I have been able to run tomcat on port 80 under a "tomcat" user.
It seems like the latest versions of Fedora require that tomcat either be
On Feb 7, 2012, at 6:14 PM, Ole Ersoy wrote:
> Hi,
>
> In the past I have been able to run tomcat on port 80 under a "tomcat" user.
> It seems like the latest versions of Fedora require that tomcat either be run
> as root or requests to 8080 have to be redirec
Ole Ersoy wrote:
Hi,
In the past I have been able to run tomcat on port 80 under a "tomcat"
user. It seems like the latest versions of Fedora require that tomcat
either be run as root or requests to 8080 have to be redirected using
iptables. Can anyone confirm this?
What yo
Hi,
In the past I have been able to run tomcat on port 80 under a "tomcat" user.
It seems like the latest versions of Fedora require that tomcat either be run as root or
requests to 8080 have to be redirected using iptables. Can anyone confirm this?
start
INFO: Cluster is about to start
On Mon, Nov 28, 2011 at 14:39, Konstantin Kolinko wrote:
> 2011/11/28 Óscar Frías Barranco :
> > Hi.
> >
> > I want to start Tomcat 6.0.33 (running on port 80) from the command line
> of
> > a non-root user. I have s
2011/11/28 Óscar Frías Barranco :
> Hi.
>
> I want to start Tomcat 6.0.33 (running on port 80) from the command line of
> a non-root user. I have set the setuid flag in the jsvc binary to
> "convert" the non-root user to root at the time of execution. Then the
> jsvc
Óscar Frías Barranco wrote:
Hi.
I want to start Tomcat 6.0.33 (running on port 80) from the command line of
a non-root user. I have set the setuid flag in the jsvc binary to
"convert" the non-root user to root at the time of execution. Then the
jsvc binary is executed with the &quo
Hi.
I want to start Tomcat 6.0.33 (running on port 80) from the command line of
a non-root user. I have set the setuid flag in the jsvc binary to
"convert" the non-root user to root at the time of execution. Then the
jsvc binary is executed with the "--user tomcat" parameter
fferent port
> (lets say, 8081 and 8082), and using IPTables NAT (and Tomcat host
> virtualization) to redirect some domains to some hosts inside a certain
> Tomcat, and some other domains in certain other virtual hosts inside other
> Tomcat. All the domains can use port 80 from the cl
ables NAT (and Tomcat host
> virtualization) to redirect some domains to some hosts inside a certain
> Tomcat, and some other domains in certain other virtual hosts inside other
> Tomcat. All the domains can use port 80 from the clients point of view, but
> inside are managed with dif
On 05/11/2011 08:35 PM, Brian Braun wrote:
IPTables NAT
Check the
http://www.quantumg.net/portforward.php
It's a single .cpp file if you don't need gui.
There is also more advanced (ipfilter like util)
http://www.hsc.fr/ressources/outils/pktfilter/
Think that you can even use PuTTY for that.
, and some other domains in certain other virtual hosts inside other
Tomcat. All the domains can use port 80 from the clients point of view, but
inside are managed with different ports.
Can I do the same in Windows Server 2008? If so, which tools do I use in
Windows itself to do those NAT mappings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 4/12/2011 5:18 PM, Brian Braun wrote:
> I'm improving my apps frecuently, so everytime I do it I need to upload a
> new WAR file. When that happens, I face the leaking problem that so far I
> haven't solved.
What leaking problem?
- -chris
Hi Chris,
I'm improving my apps frecuently, so everytime I do it I need to upload a
new WAR file. When that happens, I face the leaking problem that so far I
haven't solved. For that reason, I'm restarting Tomcat. My new app should
not be hosted in the same Tomcat instance for that reason.
I will
Thanks, I will read that.
On Mon, Apr 11, 2011 at 7:19 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Brian Braun [mailto:brianbr...@gmail.com]
> > Subject: Re: Two Tomcat 7.0.11 installations in the same Linux instance,
> running both on port
- Original Message (edited)
> Subject: Two Tomcat 7.0.11 installations in the same Linux instance, running
>both on port 80, without conflicts?
> I'm considering a parallel Tomcat installation in the same
> Linux VPS, both running at the same time. I perfectly know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 4/11/2011 6:52 PM, Brian Braun wrote:
> I have a new project, for a web service that must be running all the time.
> It should never be offline, and if it does, my clients will leave me, so I
> can not run this app in the same Tomcat install
> From: Brian Braun [mailto:brianbr...@gmail.com]
> Subject: Re: Two Tomcat 7.0.11 installations in the same Linux instance,
> running both on port 80, without conflicts?
> Is it so easy? wow, I thought it was going to be more complex. Thanks!
Forgot to mention that you can either
1 - 100 of 200 matches
Mail list logo
