Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1129511F58 for ; Sat, 5 Apr 2014 20:38:21 +0000 (UTC) Received: (qmail 87975 invoked by uid 500); 5 Apr 2014 20:38:20 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 87248 invoked by uid 500); 5 Apr 2014 20:38:18 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 86647 invoked by uid 500); 5 Apr 2014 20:38:17 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 86642 invoked by uid 99); 5 Apr 2014 20:38:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Apr 2014 20:38:16 +0000 Date: Sat, 5 Apr 2014 20:38:16 +0000 (UTC) From: "chris snow (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CLOUDSTACK-3219) Allow ports other than 80,443 and 8080 in Register Template URL. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960462#comment-13960462 ] chris snow edited comment on CLOUDSTACK-3219 at 4/5/14 8:38 PM: ---------------------------------------------------------------- On a development environment where I have xen, xapi and cloudstack running in jetty, all of the allowed ports are already used up. It would be good if there was someway to disable this check so I can run a local web server (e.g. python -m SimpleHTTPServer 8888) for serving templates. Update: As a workaround, I've got cloudstack running on a different port (9999): {code:xml} diff --git a/client/pom.xml b/client/pom.xml index 3995f6e..8d07973 100644 --- a/client/pom.xml +++ b/client/pom.xml @@ -359,7 +359,7 @@ stop-jetty - 8080 + 9999 60000 {code} was (Author: snowch): On a development environment where I have xen, xapi and cloudstack running in jetty, all of the allowed ports are already used up. It would be good if there was someway to disable this check so I can run a local web server (e.g. python -m SimpleHTTPServer 8888) for serving templates. Update: As a workaround, I've got cloudstack running on a different port (9999): {code:xml} vagrant@devcloud:/run/sr-mount/f6147c21-daa4-2d02-56e7-c06660a75ee4$ cat ~/gitdiff diff --git a/client/pom.xml b/client/pom.xml index 3995f6e..8d07973 100644 --- a/client/pom.xml +++ b/client/pom.xml @@ -359,7 +359,7 @@ stop-jetty - 8080 + 9999 60000 {code} > Allow ports other than 80,443 and 8080 in Register Template URL. > ---------------------------------------------------------------- > > Key: CLOUDSTACK-3219 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3219 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the default.) > Reporter: Thomas O'Dowd > > I'd like to be able to download templates from our object store server which is using port 18080. Currently I have to choose port 8080 and forward port 8080 to 18080 on our object store server which is not so good. Is there any reason to limit the ports and if not, can we open them up. > Currently, if I give port 18080, I get the following pop-up error: > "Only ports 80, 8080 and 443 are allowed" -- This message was sent by Atlassian JIRA (v6.2#6252)