If you have a single certificate, a single IP, and multiple assp servers behind the router, why not just use different ports for each web interface:
https://yourname:1234/ https://yourname:1234/ etc? On Tue, May 25, 2010 at 7:22 PM, Jean-Pierre van Melis <[email protected]>wrote: > I have a somewhat strange feature request. > I'm using a reverse proxy (pound) to access the different webservers within > my network. I installed this reverse proxy on my SoHo-router and I don't > need all kind of different ports to access certain servers. The reverse > proxy works like a traffic controller and looks at the hostname and then > points to the right webserver. > > This reverse proxy can also work on HTTPS-connections. Because a wildcard > certificate is quite expensive and a 1-domain certificate can even be had > for free (https://startssl.com) this hostname can't change. I can still > direct the traffic to different servers by looking at the URL. > > If the ASSP's webif could take an optional URL it would make it possible > for me to access my ASSP's webif with https. The https-traffic would be > terminated at the reverse proxy which in turn make a http-connection with > ASSP. > > It would also make it possible to manage several ASSP's using 1 hostname > and 1 certificate. > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Assp-test mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
