Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

"custName/appName"/

 

mysite/

 

 

index.html

Status Page

This page is full of links and information for using the environment, getting more help and documentation, and to provide information about your instance and its configuration.

  • WebDav urls: The kproxy or DAVPortal urls you can use to modify your site files

Getting connected to upload content

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.Your Status

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 page has the links you need to access your instance's WebDAV connection.

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.

...

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.

DAV Access Control

Access to the key generation page of DAVPortal is restricted to valid-user. Access to the DAV share itself by default is restricted to the permit created with your Static Web Hosting instance. This is to allow the use of the require netid directive in combination with DAVPortal. Though anyone with a NetID can receive a DAVPortal key for your instance, by default, only those in the permit will be able to actually access the share. The rest of the configuration is up to you - please feel free to adjust it to your needs through the use of .wdaccess files (see "Opening and Restricting Access", below).

Opening and Restricting Access

...

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.

A recommended layout is to use subfolders to organize your site, rather than to put all of your pages in the base directory. Your splash page will show information like:

...

.

Organizing your site into folders like...

...