FastCGI is an extension of the CGI way of doing things. FastCGI will exec your program one time instead of once-per-request. Your program must then handle the input. Using available libraries, it is simple to use FastCGI. Here are a few examples in various interpreted languages.
We recommend that if you need to setup a WordPress blog that you use the OIT blogs.princeton.edu service.
In January 2011, we transitioned from Web Servers running in Solaris/SPARC Zones to Linux/x86_64 Virtual Machines. In addition to the change in architecture, there will be some changes to versions of PHP and supporting libraries. This page describes the changes in detail and provides information so that users who maintain web sites on the CS web servers can transition smoothly.
Central Authentication Service (CAS) is a single sign-on protocol designed to allow potentially untrusted web applications to authenticate users against a trusted central server. Applications that authenticate with CAS never see the users credentials, since the authentication happens only on the CAS server. According to University policy, web applications or pages which require access by members of the campus community are required to use CAS.
Note: the methods described here are still available and still work, but University policy requires the use of the Central Authentication Service (CAS) protocol for authentication of members of the campus community. See our page on CAS for more information.
This tutorial covers web-based user authentication using htaccess. Web-based authentication denies web access to visitors who do not give a valid username and password. This feature allows people to restrict access to certain directories.
The department web server does support the use of CGI Scripts, and these can be written in any language. The only requirements are that the filename ends in .cgi in order to be recognized by the server as a valid CGI script, and if you're using a compiled language (C, for instance), that it be compiled on our cycles machines. Our web servers all run Linux.
The maintance of our public facing website is handled by a variety of staff. While the technical staff maintains the infrastructure that serves web pages and maintains the file systems and databases that store the content, we "own" very little of the data. This document describes how each section is maintained.
Contents:
All members of the department may create a personal home page. In addition, faculty, research scholars, and staff can edit their profile page in addition to their personal web pages. Instructions for profile pages can be found here.
