Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 14271 invoked from network); 1 May 2003 10:25:16 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 1 May 2003 10:25:16 -0000 Received: (qmail 23822 invoked by uid 97); 1 May 2003 10:27:29 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 23815 invoked from network); 1 May 2003 10:27:28 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 1 May 2003 10:27:28 -0000 Received: (qmail 13458 invoked by uid 500); 1 May 2003 10:25:07 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 13438 invoked from network); 1 May 2003 10:25:06 -0000 Received: from viefep15-int.chello.at (213.46.255.19) by daedalus.apache.org with SMTP; 1 May 2003 10:25:06 -0000 Received: from localhost ([80.110.240.41]) by viefep15-int.chello.at (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030501102515.ITAH1476.viefep15-int.chello.at@localhost> for ; Thu, 1 May 2003 12:25:15 +0200 In-Reply-To: <3EB0BF34.9070201@apache.org> To: "Tomcat Developers List" Subject: Re: why is the manager deploy command disabled... MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0 September 26, 2002 Message-ID: From: "Johannes Fiala" Date: Thu, 1 May 2003 12:28:31 +0200 X-MIMETrack: Serialize by Router on Developer1/Johannes Fiala(Release 6.0|September 26, 2002) at 01.05.2003 12:28:33, Serialize complete at 01.05.2003 12:28:33 Content-Type: multipart/alternative; boundary="=_alternative 00398B15C1256D19_=" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --=_alternative 00398B15C1256D19_= Content-Type: text/plain; charset="US-ASCII" Hi Remy, Maybe it should be noted that /deploy is handled at doPut. (btw, it does a PUT request :). BTW - Who is responsible for the manager app? I thought about extending it to an AXIS service and posted an outline how it could be working to the Tomcat-userlist. It would be nice to have a server-side consistency-check of the WAR file (using an MD5 attachment or a request parameter inside the Url), so broken JARs etc. don't occur if the connection to the Tomcat server is lousy. Johannes Remy Maucherat 01.05.2003 08:31 Please respond to "Tomcat Developers List" To Tomcat Developers List cc Subject Re: why is the manager deploy command disabled... John Cahill wrote: > in Tomcat 4.1.24? > > in org.apache.catalina.servlets.ManagerServlet, > > at line 342, we find the comment... > // Process the requested command (note - "/deploy" is not listed here) > > and indeed, there is no way for the deploy function to be called. This > disables calls to the manager deploy function and results in the unknown > command message returned to the user. > > Is there something wrong with the deploy function that caused the > developer to disable the function? deploy does a POST, not a GET. Remy --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org --=_alternative 00398B15C1256D19_=--