[Seaside] Seaside and HTTPS (for testing locally)
pdebruic at gmail.com
Fri Jun 30 00:28:43 UTC 2017
On linux or mac, for development, and if you don't want to redirect through
nginx or apache, you can make a self signed cert:
And make a subclass of ZnZincServerAdaptor with #defaultZnServer overridden
^(ZnSecureServer on: self port)
And then start it with:
| adaptor server |
adaptor := ZnZincServerAdaptor startOn: 8080.
server := adaptor default server.
And report back if it fails as I haven't tested the above but it should
work. YMMV etc etc etc
Torsten Bergmann 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?
> seaside mailing list
> seaside at .squeakfoundation
View this message in context: http://forum.world.st/Seaside-and-HTTPS-for-testing-locally-tp4952970p4952977.html
Sent from the Seaside General mailing list archive at Nabble.com.
More information about the seaside