[Seaside] Seaside and HTTPS (for testing locally)

Torsten Bergmann astares at gmx.de
Fri Jun 30 00:01:38 UTC 2017

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?


More information about the seaside mailing list