Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Need help with URL redirecting
To: users@tomcat.apache.org
References: <CAOKpjz_4VNO8dzb=bwfWC37t4rbG4rS7hdZAywD=PTOBXwibWA@mail.gmail.com>
 <57641F65.8050508@ice-sa.com>
 <CAOKpjz87qJPB9F7HDEfd-2L3AWAE-+sNwgAUy765b6M-tm_OSw@mail.gmail.com>
 <576451DC.60603@ice-sa.com>
 <CAOKpjz8AJxdRmRgMH-BhXMiowumoOT8AgvPPBUSran1vLcV5Nw@mail.gmail.com>
 <14d06e1a978048d0bdf80e9e31e3c4a4@EXCAMB03.rpega.com>
 <CAOKpjz9dPbyfvc+irknb9RrN14b4XA+GZ0ZQ0zguQ+=rbHjfOA@mail.gmail.com>
 <ef54d07b-375c-cd63-970f-af0e997a7e97@christopherschultz.net>
From: =?UTF-8?Q?Andr=c3=a9_Warnier_=28tomcat=29?= <aw@ice-sa.com>
Message-ID: <5768903A.2080404@ice-sa.com>
Date: Tue, 21 Jun 2016 02:54:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <ef54d07b-375c-cd63-970f-af0e997a7e97@christopherschultz.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Tue, 21 Jun 2016 00:54:33 -0000

On 20.06.2016 23:57, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sean,
>
> On 6/20/16 2:26 PM, Sean Son wrote:
>> On Mon, Jun 20, 2016 at 12:53 PM, Mekkelsen Madden, Steve <
>> Steve.MekkelsenMadden@pega.com> wrote:
>>
>>> One thing you could do is have an entry in your webapps\ROOT
>>> folder called like: MyAppRedirect.html  (name can be anything)
>>> Inside the file you need something like: <META
>>> HTTP-EQUIV="Refresh" CONTENT="0; URL=../myApp/connection ">
>>>
>>> In your conf\web.xml at the bottom of it, you'll see 3 lines
>>> shown below: <welcome-file-list>
>>> <welcome-file>index.html</welcome-file>
>>> <welcome-file>index.htm</welcome-file>
>>> <welcome-file>index.jsp</welcome-file> </welcome-file-list>
>>>
>>> Change this to point to your MyAppRedirect.html page.
>>> <welcome-file-list>
>>> <welcome-file>MyAppRedirect.html</welcome-file>
>>> </welcome-file-list>
>>>
>>> That's a simple way to redirect your application.  Your DNS /
>>> reverse proxy could take care of the port # and users only need
>>> to call your application by name
>>> (https://callMyApplication.domain.com) when the DNS/reverse proxy
>>> redirects it to the server's port say 8088, the html file appends
>>> the remaining portion of the url to what the users typed.
>>>
>>>
>>> -----Original Message----- From: Sean Son
>>> [mailto:linuxmailinglistsemail@gmail.com] Sent: Monday, June 20,
>>> 2016 12:42 PM To: Tomcat Users List <users@tomcat.apache.org>;
>>> aw@ice-sa.com Subject: Re: Need help with URL redirecting
>>>
>>> On Fri, Jun 17, 2016 at 3:39 PM, André Warnier (tomcat)
>>> <aw@ice-sa.com> wrote:
>>>
>>>> Hi. Another tip : on his list,mit is preferred if you respond
>>>> in or below the previous text. That's why I moved your previous
>>>> answer. It makes it easier to follow the conversation without
>>>> having to scroll back and forth all the time.
>>>>
>>>>>
>>>>
>>>>>
>>>>> On Fri, Jun 17, 2016 at 12:03 PM, André Warnier (tomcat)
>>>>> <aw@ice-sa.com> wrote:
>>>>>
>>>>> On 17.06.2016 17:03, Sean Son wrote:
>>>>>>
>>>>>> Hello all
>>>>>>>
>>>>>>> I am new to the list. This is what i am trying to do but
>>>>>>> need help on:
>>>>>>>
>>>>>>>
>>>>>>> I have a webapp running on tomcat 8:
>>>>>>> https://myapp.example.com:8443/myapp
>>>>>>>
>>>>>>> I am going to set up a DNS record myapp.example.com which
>>>>>>> will point to the IP address of the tomcat server that
>>>>>>> hosts the webapp.. I want this new DNS record
>>>>>>> myapp.example.com to redirect to
>>>>>>> https://myapp.example.com:8443/myapp. In other words, I
>>>>>>> want the URL to redirect port 80 to the URL for the
>>>>>>> webapp automatically so the users will not have to enter
>>>>>>> in the port number whenever they want to browse to the
>>>>>>> webapp. I tried doing research on google and I was not
>>>>>>> able to find a straight forward way of doing this. Any
>>>>>>> help is greatly appreciated!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The first thing you would have to check, is whether port
>>>>>>> 80 is still
>>>>>> free on that server, or if there is already another
>>>>>> webserver (e.g. Apache httpd) using it.
>>>>>>
>>>>>> The second thing to clarify is whether, apart from "myapp",
>>>>>> there are other web applications (not called "myapp") which
>>>>>> you are running or would want to run under Tomcat on that
>>>>>> server. If not, then you might want to run your application
>>>>>> as the *default* application, so that users would get to it
>>>>>> with the URL " https://myapp.example.com:8443/", instead of
>>>>>> " https://myapp.example.com:8443/myapp". To do this first,
>>>>>> have a look at : http://wiki.apache.org/tomcat/HowTo and
>>>>>> look at #17 : How do I make my web application be the
>>>>>> tomcat default application
>>>>>>
>>>>>> It will just be easier if you clear up the above points
>>>>>> first, because there are multiple possibilities, and it
>>>>>> narrows down the scope of the tips we can provide.
>>>>>>
>>>>>>
>>>> On 17.06.2016 18:43, Sean Son wrote:
>>>>
>>>>> Hello Andre
>>>>>
>>>>> thank you for your response.
>>>>>
>>>>> There are no other webservers running on this machine. There
>>>>> are other web apps as well, but the only way to access them
>>>>> is through myapp. So should I deploy myapp as the default app
>>>>> ?
>>>>>
>>>>>
>>>> Yes, I think that it will make the rest easier. So do that, as
>>>> per the instructions above, and then we will continue.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------
> - -
>>>>
>>>>
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>> Thank you for the tidbit about how to reply :) So I used number
>>> 17 from the website and i deployed the war file as the ROOT.war
>>> file.  What should the next steps be?
>>>
>>>
>>> I thank you again for all of your help!
>>>
>>
>>
>> Thank you Steve for the suggestion. Will this work with out using a
>> reverse proxy? My management told me not to use a reverse proxy
>
> Yes, you can do this without a reverse proxy, but removing the port
> number can be a bit of an issue, which is why a reverse proxy is
> sometimes recommended: it's just easier that way -- especially if
> another web server is already available for that purpose.
>
> For more help, you'll have to give us more information about your
> environment: OS, other services already available on the network, etc.
> For example, if an appropriate reverse proxy is already available,
> then you can point your DNS record to that proxy, and use a virtual
> host for that domain name. Then, proxy everything to your Tomcat instanc
> e.
>

Actually, I was thinking of using Tomcat only, and configuring 2 <Host> :
- one to listen on port 80, with a single and simple default app which sends back a 
"permanent redirect" to the other Host
- one to listen on the HTTPS port, with the real application
(or if not possible with 2 Hosts, then 2 separate Tomcat instances).
But yes, it would be simpler with a reverse proxy in front.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org