[Geomoose-users] automatically redirecting geomoose http to https using apache

[James Klassen]

I'm not sure about this.  Redirect is supposed to work with everything
under the circumstances configured path so the /app1/ lines are redundant
to the / line.  Also, IIRC you need to prevent a redirect loop where the
https site continually redirects to itself.

You also need both an http site (on port 80, without sslengine) to at a
minimum host the redirect and an https site (on port 443, with sslengine
on).  Since you say both http and https are working now, but no automatic
redirect, I don't understand how that works (where one apache instance is
handling both) without already having the two virtual hosts already defined
somewhere.


On Thu, Mar 29, 2018, 16:40 TC Haddad <tchaddad at gmail.com> wrote:

>
> Before going to virtual hosts,
>
> Since you already have https working on the root, and only have one
> domain, I would try simply augmenting the redirects you have put in place
> to include permanent redirects for the relevant apps.
>
> You already have:
>
> Redirect permanent /   https://www.mysite.com/
> <https://www.mysite.com/app1/>
>
> you could add:
>
> Redirect permanent /app1/   https://www.mysite.com/app1/
>
> Redirect permanent  /app2/ https://www.mysite.com/app2/
>
> Redirect permanent /app3/  https://www.mysite.com/app3/
>
>
>
> On Thu, Mar 29, 2018 at 1:20 PM, Dan Little <theduckylittle at gmail.com>
> wrote:
>
>> I would suggest first re-writing your Apache configuration to use a
>> VirtualHost on port 80 that serves your current data.  Then do the
>> transition.
>>
>> On Thu, Mar 29, 2018 at 3:19 PM, Mark Volz <MarkVolz at co.lyon.mn.us>
>> wrote:
>>
>>> Dan,
>>>
>>>
>>>
>>> Thank you for your reply.  I noticed that wiki, and a few others seemed
>>> to favor using virtual host to get the job done.   I noticed <VirtualHost
>>> _default_:443> is part of httpd-ssl.conf.  However, <VirtualHost *:80> is
>>> not found in any of the configuration files.  Do we just add virtual host
>>> right in httpd.conf?
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Sincerely,
>>>
>>> *Mark Volz, GISP*
>>>
>>>
>>>
>>> *From:* Dan Little [mailto:theduckylittle at gmail.com]
>>> *Sent:* Thursday, March 29, 2018 3:05 PM
>>> *To:* Mark Volz <MarkVolz at co.lyon.mn.us>
>>> *Cc:* geomoose-users at lists.osgeo.org
>>> *Subject:* Re: [Geomoose-users] automatically redirecting geomoose http
>>> to https using apache
>>>
>>>
>>>
>>> Not really a GeoMoose question but...
>>> https://wiki.apache.org/httpd/RedirectSSL
>>>
>>>
>>>
>>> Bashing "apache forward http to https" will also lead you to a number of
>>> useful guides on the subject. :-)
>>>
>>>
>>>
>>> On Thu, Mar 29, 2018 at 3:02 PM, Mark Volz <MarkVolz at co.lyon.mn.us>
>>> wrote:
>>>
>>> Hello,
>>>
>>>
>>>
>>> Similar to the demo.geomoose.org site, I am trying to find a way to
>>> automatically redirect my geomoose web traffic from http:// to https://
>>> using Apache.  It is my understanding that Google will start shaming non
>>> https:// websites.  If anyone has any notes as far as how to set it up
>>> please let me know.   Thus far I can get https:// working if a user
>>> manually types in https:// however the automatic redirection is failing.
>>>
>>>
>>>
>>> Thank You!
>>>
>>>
>>>
>>> Sincerely,
>>>
>>> *Mark Volz, GISP*
>>>
>>> *Lyon County GIS Coordinator*
>>>
>>>
>>> _______________________________________________
>>> Geomoose-users mailing list
>>> Geomoose-users at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> Geomoose-users mailing list
>> Geomoose-users at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/geomoose-users
>>
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20180330/ac976cbc/attachment-0001.html>