| Table of Contents | ||||
|---|---|---|---|---|
|
...
Our old userpages system made a distinction between dynamic and static content. All dynamic content was accessed using the www.usercgi user while static content was accessed using the www.userpages user. For the new version of userpages www.userpages is used to serve all content. For the majority of our users, this change won't be noticed, but if you made extensive use of AFS permissions on your site, especially when it comes to dynamic content that writes to your webspace, your AFS permissions may need to be adjusted. You'll want to ensure that www.userpages has userpages has all of the privileges that www.usercgi has. Please refer to the openAFS documentation or submit a support ticket for more information on updating your AFS permissions.
...
Neither UMBC nor DoIT will take responsibility for the security or integrity of files stored in areas where the www.userpages AFS user has read or write access. We also ask that any user asking for "input" on web forms that store data in those areas make it clear that any information entered on such forms is stored using an insecure method.
Available Scripting Languages
| Language | File Extension | How To Use |
|---|---|---|
| PHP 5.4 | .php | Any content in a file ending in .php will be interpreted by PHP |
| Perl 5.16 | .cgi | Begin the file with "#!/usr/bin/perl". All content below that line will be interpreted by Perl |
| Python 2.7.5 | .cgi | Begin the file with "#!/usr/bin/python". All content below that line will be interpreted by Python |
| Ruby 2.0 | .cgi | Begin the file with "#!/usr/bin/ruby". All content below that line will be interpreted by Ruby |
...