[Info-vax] Using VMS for a web server

[Rich Jordan]

On Wednesday, June 3, 2015 at 8:35:41 AM UTC-5, Dirk Munk wrote:
> I've always been in favour of using VMS for a web server. The reason is 
> quite simple, VMS is quite save out of the box (now Hoff is going to 
> explain to us that other operating systems improved very much, and that 
> certain aspects of VMS are not as save any more :-) ), and that it is 
> unknown to the script kiddies.
> 
> Secure web servers are vitally important for companies and institutions, 
> so a save web server can be a selling point.
> 
> There are three web server packages for VMS: OSU, WASD and Apache (aka 
> Compaq Secure Web Server CSWS, these days HP Secure Web Server but still 
> CSWS ?!?). I've worked with CSWS in the past, it seemed the natural 
> choice given the popularity of Apache - at least at the time.
> 
> I've been reading more on WASD, and more specifically on the performance 
> and security aspects. Performance wise, WASD is much better than CSWS, 
> and I've read about certain security problems with CSWS (can't find the 
> link again I'm afraid). WASD is a 'real' VMS product instead of a 
> Unix/Linux product made to run on VMS, like Apache is.
> 
> Also, in general the popularity of Apache is dwindling in favour of the 
> Microsoft web server. The latter seems to be much faster.
> 
> So now I wonder if it wouldn't be better to focus on WASD instead of 
> CSWS as the standard web server for VMS. The Australian company VMS 
> Software Services Pty and VSI and much more comparable than was the case 
> with Compaq or HP.  Together the two might be able to build a set of 
> nice web server products for VMS.
> 
> As usual, your thoughts please.

When I was running a VMS webserver at home (with Joomla on top of PHP, etc) I was using the HP provided Apache server, and recommending it.  Today I don't; it may be somewhat easier to get J-random piece of webware running on it but HP just flat doesn't support it; they are years behind on versions and updates.

When a customer had a problem with an ancient version of WASD, Mark Daniel was very helpful in determining the cause of the problem, and finding a workaround that didn't involve an upgrade (much as we would have liked to do that).  WASD is being maintained and improved.  You can get a lot of additions that will work with it (just not from HP and so not "the standard" such as it is).

If I get the opportunity to put up a VMS webserver again it will be on WASD.