There are a variety of ways to get help with your entity's website:

1. The AskIT website (www.uwyo.edu/askit) provides multiple how-to and FAQ documents for UW Web site development as well as links to other Web development online resources.
    
2. UW Institutional Marketing provides institutional consultation for websites managed through the UW Content Management System (CMS) on an appointment basis. See the UW Institutional Marketing site (www.uwyo.edu/publicrelations/marketing/website.html) for more information.
    
3. IT provides training opportunities to UW faculty and staff on a variety of topics and for a variety of applications used at UW. See the IT Training website (www.uwyo.edu/infotech/services/training/) for more information.
    
4. If you are unsure of the services or support offered, the best initial contact for anything computer related, including your Web sites, is the IT Help Desk at 766-HELP, option 1, or userhelp@uwyo.edu. They can help determine the best path for your question or request and route it accordingly to get it resolved as efficiently as possible.

IT maintains a standard naming convention for UW websites to lessen the affects of attacks to web servers coming in with strings that contain non-standard characters. These standards will help to secure the UW web servers as well as help to minimize problems with various web software programs.  

Website names can contain

• the standard set of characters A thru Z and numbers 0 thru 9
   
• the following non-standard characters only
    - (dash)
   _ (underscore)
   
• 15 characters or less

Website names can not contain

• spaces

Each website is allocated 1GB of space free of charge. If an entity wants additional space beyond the 1GB limit, it is available in 1GB increments for $2 per year. Additional space can be requested through your IT user consultant (www.uwyo.edu/InfoTech/services/helpdesk/uc/).

Yes. UW sites can be restricted in one of two ways:

NOTE: A site as a whole is either restricted or not. Certain directories within a site cannot be restricted while others are not restricted. If you need to restrict a specific directory within a site, you will need to request a new site, request that it be restricted, and then move the pages you want restricted to the new site.

1. Single username and password restriction: A specific username and password can be provided for each site, and the author of the site can give this information out to any individual they want to be able to browse the site. When an individual tries to browse to the site, they will be prompted to enter the username and password before they are able to see any of the pages within the site.
   
   The username will be created to match the name of the site (i.e. www.uwyo.edu/class5 would have a username of class5). The password can be determined by the author of the site.
    
2. Existing domain security group restriction: A site can be restricted to only allow members of an existing domain security group to browse the site. A site can be restricted to only allow browse access to individuals with a UWYO domain account, with either UWSTUDENTS or UWEMPLOYEES group affiliation, a specific college affiliation, or a specific department affiliation.
   
   NOTE: At this time, we do not create, populate, or manage domain security groups other than those recognized by Human Resources as a UW college or department.
   

Access to a basic website on WWW or WEBDEV can be gained in the following ways:  

• You can access it via the LAN share by selecting the Start menu, selecting Run, and typing in \\www\sitename$ (or \\webdev\sitename$) or by mapping a network drive to \\www\sitename$ (or \\webdev\sitename$). See How to Map a Network Drive (www.uwyo.edu/askit/displaydoc.asp?askitdocid=239&parentid=1) for instructions on mapping a drive in Windows.
   
• See How to Access Your Web Share through WyoSecure VPN
   
• If you are using a Mac, please use the following instructions based on the location of your site:
  
  In the Go menu select Connect to Server. In the address field type the URL of your site using the following syntax:
  
  
  • for www.uwyo.edu use smb://longhorn.uwyo.edu/sitename$
    
  • for webdev.uwyo.edu use smb://hardcase.uwyo.edu/sitename$
    
  • for uwstudentweb basic sites use smb://rawhide.uwyo.edu/username$

Access to the UW Content Management System is managed by UW Institutional Marketing. Training is mandatory before access is granted to the system. A schedule of CMS training classes is available at http://www.uwyo.edu/infotech/services/training/schedule.asp.

Also see How to Access Your Web Share through WyoSecure VPN.

Yes. All official UW websites that are managed through the CMS use standard branded templates that provide a consistent layout and navigation structure throughout the primary UW website. Inclusion of the UW brand elements on a non-CMS site must be approved by Institutional Marketing before a site is developed. Please contact webhelp@uwyo.edu for more information.

Yes, to request a redirect please go to the UW Central Site Requests site (https://uwadmnweb.uwyo.edu/centralsiterequests/) and fill out the form under Request WWW Redirect Work.

See the UW DNS Web Name Hosting FAQ (www.uwyo.edu/askit/displaydoc.asp?askitdocid=647&parentid=1).

To accommodate the request for web log data for websites located on the UW central servers, the following methods of providing web log files are available.

1. Statistics are available at http://webdev.uwyo.edu/web_statistics/
2. It is possible for more sophisticated users to access the entire website logs that are generated, copy them to their computer, and manipulate them any way they need to. Access to the website logs is gained via a LAN share: select the Start menu, click Run, and type \\servername\web_logs$\, where servername is the web server your site resides on You can then drill down to the specific log files you are interested in. Log files are kept for each individual virtual web server. Only Web logs for the previous six months will be kept, and if space becomes an issue, it may be necessary to decrease that timeframe in the future.
3. Though statistical analysis is not provided for DNS hosted sites, access to the raw log files is provided for you to process manually. The share location for the files can be accessed by going to \\servername\web_logs$, where servername is the main part of your DNS hosted site's name. For example, if your site is named business.uwyo.edu, the share is \\business\web_logs$; if your site is named www.sixthmanclub.org, the share is \\sixthmanclub\web_logs$.

• If your site is a UW Content Management System site, go to http://webdev.uwyo.edu/web_statistics/ and click on the link "View Content Management Broken Link Stats."
   
• If your site is not in the UW Content Management System, you can use a broken link checking program. A freeware program called XENU is available at http://home.snafu.de/tilman/xenulink.html or you can Google (or search the Internet using another search engine) for "XENU broken link checker."

Contact UW Institutional Marketing Web Services at webhelp@uwyo.edu.

Yes. A data source name (DSN) can be created for your site to connect to a database.

The drivers to allow the usage of Access 2007 Databases are available on the web servers. This means that, if you have Access 2007, you can now use a database in this new format (.accdb) on your web site.  In order to have a DSN set up to use Access 2007 drivers:

• Please submit your request through https://uwadmnweb.uwyo.edu/centralsiterequests/ under Request Site Configuration Change
•  Check the box for Add or Remove External Data Access
•  In the text box labeled Please give a detailed explanation of any other changes you would like on this site or add additional information specify that you would like a DSN set up for ACCESS 2007.

SSE connection string example:

Provider=sqloledb;Data Source=BOUNTYHUNTER\RLDS,6008;UID=sa;Password=[YourPassword]

More information on SSE can be found at http://www.microsoft.com/sqlserver/2008/en/us/express.aspx

Resources:

• Definition of an SQL Injection
  (http://msdn.microsoft.com/en-us/library/ms161953.aspx)
• Preventing SQL Injections in ASP
  (http://msdn.microsoft.com/en-us/library/cc676512.aspx)
• Preventing SQL Injections in ASP.NET
  (http://msdn.microsoft.com/en-us/library/ms998271.aspx)
• Coding techniques for protecting against SQL Injection
  (http://forums.asp.net/t/1254125.aspx)
• Filtering SQL injection from Classic ASP
  (http://blogs.iis.net/nazim/archive/2008/04/28/filtering-sql-injection-from-classic-asp.aspx)
• Input validation for security in Classic ASP
  (http://successontheweb.blogspot.com/2008/03/input-validation-for-security-in.html)

Yes. The main UW calendar is named "Tzolk'in" and allows individual departments to submit events that can show up in a subcalendar on their websites as well as the main calendar. To request a subcalendar for your department, please contact webhelp@uwyo.edu.

Yes. See the Streaming Media Server FAQ (www.uwyo.edu/askit/displaydoc.asp?askitdocid=676&parentid=1) for more information.

See How to Use Video Content on a UW CMS Site (www.uwyo.edu/askit/displaydoc.asp?askitdocid=601&parentid=1) for more information.

Yes. See the UW Google Search Engine FAQ (www.uwyo.edu/askit/displaydoc.asp?askitdocid=688&parentid=1) for more information.

Secure Sockets Layer (SSL) is a method of securing data communications that take place over the Internet between a person's Web browser and the site they are browsing to. SSL takes all data that is passed over the Internet, encrypts it on the sending side, and decrypts it on the receiving side. The encryption and decryption process is unique to the entities involved because of a handshaking process that takes place prior to any sensitive data being transferred.

For more information on SSL and SSL certificates see the SSL FAQ (www.uwyo.edu/askit/displaydoc.asp?askitdocid=697&parentid=1).

To help ensure that confidential information cannot be compromised, SSL is now required to be used wherever this type of information might travel across any networks. Previously, SSL was available but not mandatory; however, with the increasing availability of more sophisticated hacking tools, it has become necessary to make the use of SSL mandatory.

As of March 2005, the previous optional use of Secure Socket Layer (SSL) is now required on the UW central Web servers for the following types of sites:

• Sites requiring authentication to browse them - Sites that require a login to be able to browse / view them, require SSL (i.e. type https:// before the URL of the site). Browsing regular sites that do not require a login to access them are not affected by this change.
   
• Editing FrontPage Sites - In order to edit any FrontPage-extended site on WEBDEVFP, UWADMNWEB, UWACADWEB, and UWSTUDENTFPWEB, you must use SSL (i.e. type https:// before the URL of the site) to gain edit access to the site.

For more information on SSL and SSL certificates see the SSL FAQ (www.uwyo.edu/askit/displaydoc.asp?askitdocid=697&parentid=1).