[Info-vax] HTTP and HTML File Upload Basics

[Phillip Helbig undress to reply]

In article <rmvt0j$1l1h$1 at gioia.aioe.org>, =?UTF-8?Q?Arne_Vajh=c3=b8j?=
<arne at vajhoej.dk> writes: 

> >> I cannot remember any talks about any "public facing URL" here.
> > 
> > Webservers are usually used in a public facing way and which is how
> > I used them on VMS.
> > 
> > However, the last time I ran a webserver on VMS was 15 years ago and
> > even then I was skittish about doing that.
> 
> Depends a bit on what "public" means.
> 
> A very common meaning is "visible to public internet".
> 
> And there are lots of web servers not available on the internet.

Right.

> And I would expect the vast majority of VMS web servers to not be
> available on the internet.

Right.

> If you just mean visible outside the data center / server room,
> then it is probably most web servers.

Right.

It's not uncommon to have an internal network for backend machines, 
which are perhaps all in the same data centre(s); and then a network 
internal to the company for users of those machines (as opposed to the 
technical people running them), but completely isolated from the 
internet; machines visible to the internet might be completely isolated 
from both networks above.

> >> As far as I remember from OSU (it must have been 15-20 years since
> >> I switch to the much more capable and up-to-date WASD) there is a
> >> DCL-CGI interface so the OSU server sets up some symbols for you
> >> that helps.
> >>
> >> WASD has similar processing help, of course. And probably with more
> >> functionallity.
> > 
> > Does it write the file data to a temporary file ? DCL symbols are
> > not capable of holding the contents of a file unless it's extremely
> > small.
> 
> That wa smy concern as well.
> 
> But it turned out that CGI_SYMBOLS indeed has a capability to write
> body to file.

Yes, thanks to Arne I now have a working example.