- From: Jonas Sicking <jonas@sicking.cc>
- Date: Wed, 06 Feb 2008 03:06:11 -0800
- To: Jonas Sicking <jonas@sicking.cc>, "WAF WG (public)" <public-appformats@w3.org>
Thomas Roessler wrote: > On 2008-01-31 17:43:12 -0800, Jonas Sicking wrote: > >> Must be deployable to IIS and Apache without requiring actions by the server >> administrator in a configuration where the user can upload static files, run >> serverside scripts (such as PHP, ASP, and CGI), control http headers, and >> control authorization, but only do this for URIs under a given set of >> subdirectories on the server. >> >> >> Not sure if there is a better more technical term for "URIs under a given >> set of subdirectories on the server". The idea is that the user might only >> have access to control "/~sicking" and "/trip-planner-2010" and resources >> under those directories. > > I would like this to not mention specific products of any particular > vendor. > > Please phrase this generically in terms of the user being able to > control a static resource, being able to control http headers, and > authorization. > > (I think I said that on the call already.) I really dislike mentioning specific servers too, but when I used the wording "typical" then that got lots of negative feedback too. So the only thing I can think of is to revert "IIS and Apache" back to "commonly installed servers". Other than that I'm out of ideas but would welcome other suggestions. / Jonas
Received on Wednesday, 6 February 2008 11:06:22 UTC