Known Issues and Bugs
Connecting from Off-Campus (Proxy Server)
- Error message: "Couldn't decode pre-session cookie" Hitting Refresh will attempt to resubmit your request
- Proxy server sessions "expire" after a certain period of inactivity. If you receive the above error message, refreshing your browser's window will attempt to re-join your proxy session. In some cases this may fail. You will need to close your browser and re-start the proxy server or use our bookmarklet to jump back into the proxy server.
Reviewed: March 16, 2011
- In order to access streaming media reserves, you must:
- Be a current UW student with a valid UWNetID.
- Enter a class password provided to you by your instructor.
- If you have technical difficulties accessing streaming media reserves you can try the following:
If you continue to experience issues, contact Media Center at email@example.com or visit the Technology Help desk in Odegaard Library.
- Check to be sure you are using a wired ethernet, not wireless, connection;
- Update your Flash and/or Silverlight players;
- Clear the cache on your browser;
- Try a different browser.
- Proxy autodetect feature in the Zotero browser plug-in causes seemingly random prompts for UW NetID login
- If you are prompted for a UW NetID login when trying to visit web sites you should have access to, chances are that the proxy auto-detect/redirect feature in the Zotero browser plugin is interfering with your browsing experience. To resolve this issue you will need to disable the proxy features in Zotero. A short tutorial on how to do this is available at http://faculty.washington.edu/murata/zotero/zoteroproxyconfig_med.html.
Updated: March 16, 2011
- Security Alert error dialog when accessing secure site (https://
- When attempting to access secure sites via https:// URLs (e.g., MyUW, electronic
reserves readings), the browser raises a Security Alert dialog box and complains
that the site's "security certificate has expired or is not yet valid".
- Check the system date on the client workstation; an incorrect system date
will often trigger this error message.
- Reviewed: March 16, 2011