I'll update the docs. boot.js which is the key to all boot files
automatically can identify if it was called with http or https so there is
no need for special boot files for secure connections. Take a look at
test_ssl for an example.
David Botton
On Sat, Jul 11, 2015 at 7:49 AM Björn Lundin <b.f.lun...@gmail.com> wrote:
> I am trying (with a friend) to set up
> a gnoga app via https.
>
> in README-SSL this is mentioned:
>
> "Setup your proxy to use an ssl connection and use the secure.html boot
> loader"
>
> but I cannot find any secure.html in the gnoga tree.
>
>
> doing
> wget https://snake.gnoga.com/boot.html
> wget https://snake.gnoga.com/secure.html
>
> diff boot.html secure.html
>
> reveal that secure.html is identical to boot.html
>
> what am I missing?
>
> Or is secure.html the same as boot.html ?
> Do I need a secure.html in my gnoga's html dir?
>
>
> --
> Björn
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> Gnoga-list mailing list
> Gnoga-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gnoga-list
>
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Gnoga-list mailing list
Gnoga-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnoga-list
