Welcome to Static Web Hosting. This page is designed to walk you through some of the features and areas of your Static Web Hosting space, explain how to add URLs to your site and link you to other resources.
Suggestions are always appreciated, so please let us know if there is material that is unclear, could be improved, or additions that we should make to this page. Thank you!
Every Static Web Hosting space starts out with a directory structure much like this:
"custName/appName"/ |
||
|
mysite/ |
|
|
|
index.html |
The Static Web Hosting service uses a protocol called WebDAV to provide file transfer services. It is similar in idea to FTP, but slightly different in several key ways, most significantly in that it ties in with CU WebAuth - you are able to restrict file management access to directories within your instance on a per-NetID or per-permit basis.
The webdav url for Static looks like: https://static-webdav.kproxy.cornell.edu/<custname>
Webservices will give you the appropriate directory to enter once setup is complete.
Both Windows and Macintosh have built-in WebDAV support in the operating system. Windows makes WebDAV available via Network Folders. Macintosh has WebDAV support in the Finder.
WebDAV in Windows network places are available here.
General directions Macintosh, and other clients are available here.
If you prefer, there are also several excellent third-party applications available for WebDAV connections, particularly for Macintosh, including Cyberduck, Transmit, Coda, Goliath, and more. Windows support at the moment is primarily limited to the Network Places folders provided within the operating system.
By default, your Static Web Hosting account will come with a permit. The initial membership of this permit will be the primary contact, the secondary contact, and all additional authorized users listed on the signup form. Additionally, the primary and secondary contacts for the instance will also have the update privilege to update membership to the permit via the permit interface.
This only applies if you site has CU WebAuth enabled.
Please see the guide available here.
Roughly speaking, a hostname like yoursite.cit.cornell.edu will point to a folder on the filesystem, so that visitors of http://yoursite.cit.cornell.edu will see the contents of that folder.
Organizing your site into folders like...
"yoursite"/ |
||
|
yoursite1/ |
|
|
|
index.html |
|
|
stuff.html |
|
|
pic.jpg |
|
yoursite2/ |
|
|
|
index2.html |
|
|
morestuff.jpg |
|
yoursite3/ |
. . .
and so forth.
However, you are of course free to organize your site in the best way possible for you; this is just a suggested layout based on successful site development and organization in other hosted environments here at CIT.
When you are ready to add or move additional URLs like yoursite.cornell.edu to point at your site, please submit a request to webservices, with at least a day or two of notice to ensure that we have time to coordinate DNS moves and configuration updates. If you are moving an existing URL, the more notice you can provide, the better.
When you request an additional URL be setup, we need to know a few things:
Apache configuration information for use within your htaccess files: httpd.apache.org. The default server configuration for ".htaccess" is set to:
Options FollowSymlinks IncludesNOEXEC -MultiViews AllowOverride AuthConfig FileInfo Indexes Limit Options=Indexes,IncludesNOEXEC,MultiViews |
Using CU Web Auth to open or restrict access to your application: Confluence