Re: Seaside and HTTPS (for testing locally)

Jerry Kott <[email protected]> Thu, 29 Jun 2017 17:30:57 -0700
Newsgroups	gmane.comp.lang.smalltalk.squeak.seaside
Message-ID	<[email protected]>
Or you can use SiouX/Seaside on VW8.2. It has an HTTPS server, and you can generate your own SSL certificates too. Recently browsers started blocking self-signed certificates though, so you may have a bit of work with setting up browser exceptions and/or creating your own root certificate and importing it into the browser. Neither is considered a best practice for a production system but for testing it should work.

Jerry Kott
This message has been digitally signed.
PGP Fingerprint:
A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5



> On 29-06-2017, at 5:16 PM, John McIntosh <[email protected]> wrote:
> 
> redirect via NGINX
> https://www.bjornjohansen.no/redirect-to-https-with-nginx <https://www.bjornjohansen.no/redirect-to-https-with-nginx>
> 
> On Thu, Jun 29, 2017 at 5:01 PM, Torsten Bergmann <[email protected] <mailto:[email protected]>> wrote:
> Today web development for mobile devices is very common. So one possible scenario is to
> develop with Seaside on a computer and checking the result page directly with a browser
> on the phone in the same network.
> 
> This works perfectly in a quick and simple setup (with seaside running on port 80).
> One just opens the IP address of the developer computer to access the seaside page
> over HTTP and can check how it looks on mobile.
> 
> But in recent times Google is pushing to get all website using their APIs to move from HTTP
> to the HTTPS protocol. So for same client side browser APIs (for instance for geolocation)
> the mobile chrome on Android mobile devices now returns "Only secure origins are allowed".
> 
> So such functionaliy is only allowed in the client browser when the server is on a secure
> HTTPS connections. While this makes sense for production setups one usually does not have a
> local HTTPS connection out of the box with Seaside when testing and developing an application.
> 
> What is the best way and most easy Way to locally serve Seaside with HTTPS for testing?
> How to set this up? What do people use?
> 
> Thanks
> T.
> 
> _______________________________________________
> seaside mailing list
> [email protected] <mailto:[email protected]>
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
> 
> 
> 
> --
> ===========================================================================
> John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk <https://www.linkedin.com/in/smalltalk>
> ===========================================================================
> _______________________________________________
> seaside mailing list
> [email protected]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
signature.asc (application/pgp-signature, 842 B)